Add nodes to single node gluster hyperconverged
Hi everyone, is it possible to add nodes to a single node gluster hyperconverged setup? I have 3 nodes, one has been reinstalled with single node HE and VMs migrated on it. How can I add the two other nodes to this setup? Thank you, M.
Yep, that's the whole idea of the single-node setup .You have to remove the nodes from the old Engine and then add them via Engine UI, andible or api. Best Regards,Strahil Nikolov On Fri, Aug 6, 2021 at 19:47, Mathieu Valois<mvalois@teicee.com> wrote: Hi everyone, is it possible to add nodes to a single node gluster hyperconverged setup? I have 3 nodes, one has been reinstalled with single node HE and VMs migrated on it. How can I add the two other nodes to this setup? Thank you, M. _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/WJV7ST4BQ5P2U4...
Thank you for your answer. If I follow what you say, I guess that the engine storage and the VMs storage won't be replicated on a replica 3 gluster, as it would be if I ran the 3 nodes gluster hyperconverged wizard? Moreover, I though of such a scenario to add these nodes: * manually create the replica 3 gluster volumes (engine, data, vmstore) * migrate the VMs to the replicated vmstore volume * ensure everything runs fine * backup the engine * restore the engine on the replicated engine volume Should that works? Thank you, M. Le 07/08/2021 à 10:46, Strahil Nikolov a écrit :
Yep, that's the whole idea of the single-node setup . You have to remove the nodes from the old Engine and then add them via Engine UI, andible or api.
Best Regards, Strahil Nikolov
On Fri, Aug 6, 2021 at 19:47, Mathieu Valois <mvalois@teicee.com> wrote: Hi everyone,
is it possible to add nodes to a single node gluster hyperconverged setup? I have 3 nodes, one has been reinstalled with single node HE and VMs migrated on it. How can I add the two other nodes to this setup?
Thank you,
M. _______________________________________________ Users mailing list -- users@ovirt.org <mailto:users@ovirt.org> To unsubscribe send an email to users-leave@ovirt.org <mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/privacy-policy.html <https://www.ovirt.org/privacy-policy.html> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://www.ovirt.org/community/about/community-guidelines/> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/WJV7ST4BQ5P2U4... <https://lists.ovirt.org/archives/list/users@ovirt.org/message/WJV7ST4BQ5P2U4SCSXKYB4VZAX36U4PW/>
I think that your VMs are already using the Gluster (replica 1 , a.k.a distributed volume). You might just add the new host via Engine UI, then through the UI you can create the bricks and modify the volume . Of course you can go via cli. Best Regards,Strahil Nikolov On Mon, Aug 9, 2021 at 11:32, Mathieu Valois<mvalois@teicee.com> wrote: _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/PGFZZO4PYW6ZOY...
So that way, the new hosts will copy the data from the already provisionned vmstore? Le 09/08/2021 à 11:35, Strahil Nikolov a écrit :
I think that your VMs are already using the Gluster (replica 1 , a.k.a distributed volume).
You might just add the new host via Engine UI, then through the UI you can create the bricks and modify the volume .
Of course you can go via cli.
Best Regards, Strahil Nikolov
On Mon, Aug 9, 2021 at 11:32, Mathieu Valois <mvalois@teicee.com> wrote: _______________________________________________ Users mailing list -- users@ovirt.org <mailto:users@ovirt.org> To unsubscribe send an email to users-leave@ovirt.org <mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/privacy-policy.html <https://www.ovirt.org/privacy-policy.html> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://www.ovirt.org/community/about/community-guidelines/> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/PGFZZO4PYW6ZOY... <https://lists.ovirt.org/archives/list/users@ovirt.org/message/PGFZZO4PYW6ZOYYWXCMFG6FJ7ANA47QL/>
-- téïcée <https://www.teicee.com/?pk_campaign=Email> *Mathieu Valois* Bureau Caen: Quartier Kœnig - 153, rue Géraldine MOCK - 14760 Bretteville-sur-Odon Bureau Vitré: Zone de la baratière - 12, route de Domalain - 35500 Vitré 02 72 34 13 20 | www.teicee.com <https://www.teicee.com/?pk_campaign=Email> téïcée sur facebook <https://www.facebook.com/teicee> téïcée sur twitter <https://twitter.com/Teicee_fr> téïcée sur linkedin <https://www.linkedin.com/company/t-c-e> téïcée sur viadeo <https://fr.viadeo.com/fr/company/teicee> Datadocké
If the VMs are on the replica 1 volume (and they should), converting to 'replica 3' will just copy the data between the nodes. Check in the UI the volume type , brick count, etc. I guess you will need to add the two hosts, which oVirt will automatically add them in Gluster Cluster. You can then open the UI and create the bricks and change the volume. You can also do it from cli and once adding the hosts, then they will be automatically detected properly. Always test properly on a non-prod environment. Best Regards,Strahil Nikolov On Mon, Aug 9, 2021 at 12:52, Mathieu Valois<mvalois@teicee.com> wrote: So that way, the new hosts will copy the data from the already provisionned vmstore? Le 09/08/2021 à 11:35, Strahil Nikolov a écrit : I think that your VMs are already using the Gluster (replica 1 , a.k.a distributed volume). You might just add the new host via Engine UI, then through the UI you can create the bricks and modify the volume . Of course you can go via cli. Best Regards, Strahil Nikolov On Mon, Aug 9, 2021 at 11:32, Mathieu Valois <mvalois@teicee.com> wrote: _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/PGFZZO4PYW6ZOY... -- | | Mathieu Valois Bureau Caen: Quartier Kœnig - 153, rue Géraldine MOCK - 14760 Bretteville-sur-Odon Bureau Vitré: Zone de la baratière - 12, route de Domalain - 35500 Vitré 02 72 34 13 20 | www.teicee.com | |
Currently, in the engine UI, the Volume list is empty (maybe it is because I don't have the 3 nodes joined the cluster): Even though the cli volume status shows me one brick: # gluster volume status vmstore Status of volume: vmstore Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick gluster-ov3.<snip>:/gluster_bricks /vmstore/vmstore 49154 0 Y 244859 Task Status of Volume vmstore ------------------------------------------------------------------------------ There are no active volume tasks Le 09/08/2021 à 12:12, Strahil Nikolov a écrit :
If the VMs are on the replica 1 volume (and they should), converting to 'replica 3' will just copy the data between the nodes.
Check in the UI the volume type , brick count, etc.
I guess you will need to add the two hosts, which oVirt will automatically add them in Gluster Cluster. You can then open the UI and create the bricks and change the volume.
You can also do it from cli and once adding the hosts, then they will be automatically detected properly.
Always test properly on a non-prod environment.
Best Regards, Strahil Nikolov
On Mon, Aug 9, 2021 at 12:52, Mathieu Valois <mvalois@teicee.com> wrote:
So that way, the new hosts will copy the data from the already provisionned vmstore?
Le 09/08/2021 à 11:35, Strahil Nikolov a écrit : I think that your VMs are already using the Gluster (replica 1 , a.k.a distributed volume).
You might just add the new host via Engine UI, then through the UI you can create the bricks and modify the volume .
Of course you can go via cli.
Best Regards, Strahil Nikolov
On Mon, Aug 9, 2021 at 11:32, Mathieu Valois <mvalois@teicee.com> <mailto:mvalois@teicee.com> wrote: _______________________________________________ Users mailing list -- users@ovirt.org <mailto:users@ovirt.org> To unsubscribe send an email to users-leave@ovirt.org <mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/privacy-policy.html <https://www.ovirt.org/privacy-policy.html> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://www.ovirt.org/community/about/community-guidelines/> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/PGFZZO4PYW6ZOY... <https://lists.ovirt.org/archives/list/users@ovirt.org/message/PGFZZO4PYW6ZOYYWXCMFG6FJ7ANA47QL/>
-- téïcée <https://www.teicee.com/?pk_campaign=Email> *Mathieu Valois*
Bureau Caen: Quartier Kœnig - 153, rue Géraldine MOCK - 14760 Bretteville-sur-Odon Bureau Vitré: Zone de la baratière - 12, route de Domalain - 35500 Vitré 02 72 34 13 20 | www.teicee.com <https://www.teicee.com/?pk_campaign=Email>
téïcée sur facebook <https://www.facebook.com/teicee> téïcée sur twitter <https://twitter.com/Teicee_fr> téïcée sur linkedin <https://www.linkedin.com/company/t-c-e> téïcée sur viadeo <https://fr.viadeo.com/fr/company/teicee> Datadocké
-- téïcée <https://www.teicee.com/?pk_campaign=Email> *Mathieu Valois* Bureau Caen: Quartier Kœnig - 153, rue Géraldine MOCK - 14760 Bretteville-sur-Odon Bureau Vitré: Zone de la baratière - 12, route de Domalain - 35500 Vitré 02 72 34 13 20 | www.teicee.com <https://www.teicee.com/?pk_campaign=Email> téïcée sur facebook <https://www.facebook.com/teicee> téïcée sur twitter <https://twitter.com/Teicee_fr> téïcée sur linkedin <https://www.linkedin.com/company/t-c-e> téïcée sur viadeo <https://fr.viadeo.com/fr/company/teicee> Datadocké
I have never managed gluster via the UI, but theoretically it should work from there. Maybe there is a bug. You can prepare the new bricks (don't forget to "mkfs.xfs -i size=512 /dev/vg/lv") manually, but it's more error-prone. Let's see if someone else can confirm that this (UI) behavior is expected or not. Best Regards,Strahil Nikolov On Mon, Aug 9, 2021 at 13:21, Mathieu Valois<mvalois@teicee.com> wrote: Currently, in the engine UI, the Volume list is empty (maybe it is because I don't have the 3 nodes joined the cluster): Even though the cli volume status shows me one brick: # gluster volume status vmstore Status of volume: vmstore Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick gluster-ov3.<snip>:/gluster_bricks /vmstore/vmstore 49154 0 Y 244859 Task Status of Volume vmstore ------------------------------------------------------------------------------ There are no active volume tasks Le 09/08/2021 à 12:12, Strahil Nikolov a écrit : If the VMs are on the replica 1 volume (and they should), converting to 'replica 3' will just copy the data between the nodes. Check in the UI the volume type , brick count, etc. I guess you will need to add the two hosts, which oVirt will automatically add them in Gluster Cluster. You can then open the UI and create the bricks and change the volume. You can also do it from cli and once adding the hosts, then they will be automatically detected properly. Always test properly on a non-prod environment. Best Regards, Strahil Nikolov On Mon, Aug 9, 2021 at 12:52, Mathieu Valois <mvalois@teicee.com> wrote: So that way, the new hosts will copy the data from the already provisionned vmstore? Le 09/08/2021 à 11:35, Strahil Nikolov a écrit : I think that your VMs are already using the Gluster (replica 1 , a.k.a distributed volume). You might just add the new host via Engine UI, then through the UI you can create the bricks and modify the volume . Of course you can go via cli. Best Regards, Strahil Nikolov On Mon, Aug 9, 2021 at 11:32, Mathieu Valois <mvalois@teicee.com> wrote: _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/PGFZZO4PYW6ZOY... -- | | Mathieu Valois Bureau Caen: Quartier Kœnig - 153, rue Géraldine MOCK - 14760 Bretteville-sur-Odon Bureau Vitré: Zone de la baratière - 12, route de Domalain - 35500 Vitré 02 72 34 13 20 | www.teicee.com | | -- | | Mathieu Valois Bureau Caen: Quartier Kœnig - 153, rue Géraldine MOCK - 14760 Bretteville-sur-Odon Bureau Vitré: Zone de la baratière - 12, route de Domalain - 35500 Vitré 02 72 34 13 20 | www.teicee.com | |
Moreover, when I want to add a new volume though the UI, there is no DC available then I can't : Le 09/08/2021 à 12:42, Strahil Nikolov a écrit :
I have never managed gluster via the UI, but theoretically it should work from there.
Maybe there is a bug.
You can prepare the new bricks (don't forget to "mkfs.xfs -i size=512 /dev/vg/lv") manually, but it's more error-prone.
Let's see if someone else can confirm that this (UI) behavior is expected or not.
Best Regards, Strahil Nikolov
On Mon, Aug 9, 2021 at 13:21, Mathieu Valois <mvalois@teicee.com> wrote:
Currently, in the engine UI, the Volume list is empty (maybe it is because I don't have the 3 nodes joined the cluster):
Even though the cli volume status shows me one brick:
# gluster volume status vmstore Status of volume: vmstore Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick gluster-ov3.<snip>:/gluster_bricks /vmstore/vmstore 49154 0 Y 244859
Task Status of Volume vmstore ------------------------------------------------------------------------------ There are no active volume tasks
Le 09/08/2021 à 12:12, Strahil Nikolov a écrit : If the VMs are on the replica 1 volume (and they should), converting to 'replica 3' will just copy the data between the nodes.
Check in the UI the volume type , brick count, etc.
I guess you will need to add the two hosts, which oVirt will automatically add them in Gluster Cluster. You can then open the UI and create the bricks and change the volume.
You can also do it from cli and once adding the hosts, then they will be automatically detected properly.
Always test properly on a non-prod environment.
Best Regards, Strahil Nikolov
On Mon, Aug 9, 2021 at 12:52, Mathieu Valois <mvalois@teicee.com> <mailto:mvalois@teicee.com> wrote:
So that way, the new hosts will copy the data from the already provisionned vmstore?
Le 09/08/2021 à 11:35, Strahil Nikolov a écrit : I think that your VMs are already using the Gluster (replica 1 , a.k.a distributed volume).
You might just add the new host via Engine UI, then through the UI you can create the bricks and modify the volume .
Of course you can go via cli.
Best Regards, Strahil Nikolov
On Mon, Aug 9, 2021 at 11:32, Mathieu Valois <mvalois@teicee.com> <mailto:mvalois@teicee.com> wrote: _______________________________________________ Users mailing list -- users@ovirt.org <mailto:users@ovirt.org> To unsubscribe send an email to users-leave@ovirt.org <mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/privacy-policy.html <https://www.ovirt.org/privacy-policy.html> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://www.ovirt.org/community/about/community-guidelines/> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/PGFZZO4PYW6ZOY... <https://lists.ovirt.org/archives/list/users@ovirt.org/message/PGFZZO4PYW6ZOYYWXCMFG6FJ7ANA47QL/>
-- téïcée <https://www.teicee.com/?pk_campaign=Email> *Mathieu Valois*
Bureau Caen: Quartier Kœnig - 153, rue Géraldine MOCK - 14760 Bretteville-sur-Odon Bureau Vitré: Zone de la baratière - 12, route de Domalain - 35500 Vitré 02 72 34 13 20 | www.teicee.com <https://www.teicee.com/?pk_campaign=Email>
téïcée sur facebook <https://www.facebook.com/teicee> téïcée sur twitter <https://twitter.com/Teicee_fr> téïcée sur linkedin <https://www.linkedin.com/company/t-c-e> téïcée sur viadeo <https://fr.viadeo.com/fr/company/teicee> Datadocké
-- téïcée <https://www.teicee.com/?pk_campaign=Email> *Mathieu Valois*
Bureau Caen: Quartier Kœnig - 153, rue Géraldine MOCK - 14760 Bretteville-sur-Odon Bureau Vitré: Zone de la baratière - 12, route de Domalain - 35500 Vitré 02 72 34 13 20 | www.teicee.com <https://www.teicee.com/?pk_campaign=Email>
téïcée sur facebook <https://www.facebook.com/teicee> téïcée sur twitter <https://twitter.com/Teicee_fr> téïcée sur linkedin <https://www.linkedin.com/company/t-c-e> téïcée sur viadeo <https://fr.viadeo.com/fr/company/teicee> Datadocké
-- téïcée <https://www.teicee.com/?pk_campaign=Email> *Mathieu Valois* Bureau Caen: Quartier Kœnig - 153, rue Géraldine MOCK - 14760 Bretteville-sur-Odon Bureau Vitré: Zone de la baratière - 12, route de Domalain - 35500 Vitré 02 72 34 13 20 | www.teicee.com <https://www.teicee.com/?pk_campaign=Email> téïcée sur facebook <https://www.facebook.com/teicee> téïcée sur twitter <https://twitter.com/Teicee_fr> téïcée sur linkedin <https://www.linkedin.com/company/t-c-e> téïcée sur viadeo <https://fr.viadeo.com/fr/company/teicee> Datadocké
Hi Strahil, I am not as confident as you are, that this is actually what the single-node is "designed" for. As a matter of fact, any "design purpose statement" for the single-node setup seems missing. The even more glaring omission is any official guide on how to increase HCI from 1 to 9 in steps of one, which for me would really earn the title "HCI". Anyhow, adding additional nodes for compute is easily done by adding such a node in the GUI. Expanding the Gluster underneath to additional replicas, with arbitration or full copies is also easy enough, once you have Gluster experience. I'd rather doubt the GUI would help you there and what's worse, the GUI doesn't easily tell you what it tries to do. By the time you've found and understood what it tries from the logfiles, you'd have it done on your own. Actually I find that it's much easier to replicate the storage setup on any additional node via Cockpit. So install/enable cockpit, have a look on the machine you're trying to replicate and set up LVM, VDO etc. based on the original machine. Doing the Gluster replicas based on that is much easier. That's also what I've used to replace fully failed nodes on 3 node HCI clusters. Now whether or not oVirt will then treat such a hand-made 1->3 node cluster like a 3 node HCI built by itself is something I've never tried. If I had successfully tested the 3 node to 6 and 9 node expansion, I'd perhaps be more confident. But it could just turn out that without fiddling with the postgres database in the management engine this won't happen. But since you can re-install any host to become an management engine host, again it may be worth trying (after all we'd all love to know if you made it work!). So Mathieu, bonne chance et j'espère que ça va marcher !
Actually quite a few of my 3 node HCI deployments wound up with only the first host showing up in oVirt: Neither the hosts nor the gluster nodes were visible for nodes #2 and #3. Now that could be because I am too impatient and self-discovery will eventually add them or it could be because I am using sub-part hardware (Atoms and NUCs in my home lab), which causes race conditions with Ansible (yes, that does happen with oVirt). And in those cases I wound up installing the two other nodes as an act of desperation before restarting the full re-install, either (first) without the hosted-engine option (adding it later) or just with the hosted-engine option, as if they were ordinary compute(-only) hosts. It would have the storage volumes change from being described as single to replica (even if on the Gluster level they had always been replicas) and advance the cluster to a perfectly normal 3-node HCI. But I have no way of knowing if the 3-node HCI base configuration had been injected into the management engine's database already at that point. If it wasn't, then indeed a 1-9 single step increase should basically work, but oVirt still balks at the natural progression from pure replica to erasure code volumes, against which there are many objections hard coded into oVirt Ansible and library Python code. I wish I had the time budget and physical hardware to test this, but unfortunately I can only hope someone else has.
On 2021-08-27 13:24, Thomas Hoberg wrote:
I'd rather doubt the GUI would help you there and what's worse, the GUI doesn't easily tell you what it tries to do. By the time you've found and understood what it tries from the logfiles, you'd have it done on your own.
It's an unfortunate thing that the GUI assumptions can be counter intuitive in many regards, but i can confirm you can do this in the GUI as long as the gluster volumes was created in the GUI in the first place. If not, it will not show up as a volume.
Now whether or not oVirt will then treat such a hand-made 1->3 node cluster like a 3 node HCI built by itself is something I've never tried.
It will as long as the above gluster volume requirement is met, although if using gluster for hosted engine you typically end up doing that by hand.
If I had successfully tested the 3 node to 6 and 9 node expansion, I'd perhaps be more confident. But it could just turn out that without fiddling with the postgres database in the management engine this won't happen.
I do this quite often, add hosts to compute, add bricks to a gluster volume, done deal. However we do tend to use ZFS underneath which is outside the scope of oVirt. It allows us to re-use existing storage elements (providing there is enough space) to create temporary volumes to assist in the process.
I know that the GUi should work in most setups, as oVirt is the upstream of the Red Hat Gluster Storage Console. Despite RH being an open-source company, it's also trying to sell support contracts and thus it's not an open-documentation company - they need to make money after all. I know that oVirt is 'hardcoded' (this is intentional) to replica 3 when upgrading, so you add 2 nodes, then prepare the bricks and modify the volumes to 'replica 3', then add a new cycle of 3 nodes and repeat. Best Regards,Strahil Nikolov Sent from Yahoo Mail on Android On Fri, Aug 27, 2021 at 20:58, Alex McWhirter<alex@triadic.us> wrote: On 2021-08-27 13:24, Thomas Hoberg wrote:
I'd rather doubt the GUI would help you there and what's worse, the GUI doesn't easily tell you what it tries to do. By the time you've found and understood what it tries from the logfiles, you'd have it done on your own.
It's an unfortunate thing that the GUI assumptions can be counter intuitive in many regards, but i can confirm you can do this in the GUI as long as the gluster volumes was created in the GUI in the first place. If not, it will not show up as a volume.
Now whether or not oVirt will then treat such a hand-made 1->3 node cluster like a 3 node HCI built by itself is something I've never tried.
It will as long as the above gluster volume requirement is met, although if using gluster for hosted engine you typically end up doing that by hand.
If I had successfully tested the 3 node to 6 and 9 node expansion, I'd perhaps be more confident. But it could just turn out that without fiddling with the postgres database in the management engine this won't happen.
I do this quite often, add hosts to compute, add bricks to a gluster volume, done deal. However we do tend to use ZFS underneath which is outside the scope of oVirt. It allows us to re-use existing storage elements (providing there is enough space) to create temporary volumes to assist in the process. _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/M5VC5AP6V6BV2V...
Hello, Can you check if gluster service is enabled on the cluster. To check go to compute -> cluster -> edit cluster -> you will get popup screen see there will be one naming "checkbox enable gluster services" if this checkbox is not enabled then please enable and try. On Sun, Aug 29, 2021 at 10:09 PM Strahil Nikolov via Users <users@ovirt.org> wrote:
I know that the GUi should work in most setups, as oVirt is the upstream of the Red Hat Gluster Storage Console.
Despite RH being an open-source company, it's also trying to sell support contracts and thus it's not an open-documentation company - they need to make money after all.
I know that oVirt is 'hardcoded' (this is intentional) to replica 3 when upgrading, so you add 2 nodes, then prepare the bricks and modify the volumes to 'replica 3', then add a new cycle of 3 nodes and repeat.
Best Regards, Strahil Nikolov
Sent from Yahoo Mail on Android <https://go.onelink.me/107872968?pid=InProduct&c=Global_Internal_YGrowth_AndroidEmailSig__AndroidUsers&af_wl=ym&af_sub1=Internal&af_sub2=Global_YGrowth&af_sub3=EmailSignature>
On Fri, Aug 27, 2021 at 20:58, Alex McWhirter <alex@triadic.us> wrote: On 2021-08-27 13:24, Thomas Hoberg wrote:
I'd rather doubt the GUI would help you there and what's worse, the GUI doesn't easily tell you what it tries to do. By the time you've found and understood what it tries from the logfiles, you'd have it done on your own.
It's an unfortunate thing that the GUI assumptions can be counter intuitive in many regards, but i can confirm you can do this in the GUI as long as the gluster volumes was created in the GUI in the first place. If not, it will not show up as a volume.
Now whether or not oVirt will then treat such a hand-made 1->3 node cluster like a 3 node HCI built by itself is something I've never tried.
It will as long as the above gluster volume requirement is met, although if using gluster for hosted engine you typically end up doing that by hand.
If I had successfully tested the 3 node to 6 and 9 node expansion, I'd perhaps be more confident. But it could just turn out that without fiddling with the postgres database in the management engine this won't happen.
I do this quite often, add hosts to compute, add bricks to a gluster volume, done deal. However we do tend to use ZFS underneath which is outside the scope of oVirt. It allows us to re-use existing storage elements (providing there is enough space) to create temporary volumes to assist in the process.
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/M5VC5AP6V6BV2V...
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/QJENZRPXIBFQQV...
participants (5)
-
Alex McWhirter -
Mathieu Valois -
Ritesh Chikatwar -
Strahil Nikolov -
Thomas Hoberg