probing peers in gluster after installing hosts
This is a multi-part message in MIME format. --------------050806000807090207010701 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Hi all, I created 3 clusters in unique datacenter. I installed my hosts to the first one after activating the gluster service in the cluster tab. A expected otopi installed then the vdsm-gluster rpm and everything were ok for this first cluster. The other ones weren't initially gluster ready and I wanted to activate the service after installing the host (so they were without vdsm-gluster package). But checking that item didn't do anything for these hosts, so that I had to manually install vdsm-gluster package. Then, when creating a volume, the UI told me that hosts couldn't communicate. So I had to manually probe them. This leads me to that question : is it an expected behaviour? The whole gluster job (installing appropriated package and probing peers in the cluster) should be done thanks to the UI cluster tab "gluster service". A last question : why isn't it possible to probe host on different clusters in the same datacenter, could be very useful. -- Nathanaël Blanchet Supervision réseau Pôle exploitation et maintenance Département des systèmes d'information 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet@abes.fr --------------050806000807090207010701 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </head> <body bgcolor="#FFFFFF" text="#000000"> <font size="-1">Hi all,<br> <br> I created 3 clusters in unique datacenter. I installed </font><font size="-1"><font size="-1">my hosts </font>to the first one after activating the gluster service in the cluster tab. A expected otopi installed then the vdsm-gluster rpm and everything were ok for this first cluster. <br> The other ones weren't initially gluster ready and I wanted to activate the service after installing the host (so they were without vdsm-gluster package). But checking that item didn't do anything for these hosts, so that I had to manually install vdsm-gluster package. Then, when creating a volume, the UI told me that hosts couldn't communicate. So I had to manually probe them. This leads me to that question : is it an expected behaviour? The whole gluster job (installing appropriated package and probing peers in the cluster) should be done thanks to the UI cluster tab "gluster service".<br> A last question : why isn't it possible to probe host on different clusters in the same datacenter, could be very useful.<br> </font> <pre class="moz-signature" cols="72">-- Nathanaël Blanchet Supervision réseau Pôle exploitation et maintenance Département des systèmes d'information 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 <a class="moz-txt-link-abbreviated" href="mailto:blanchet@abes.fr">blanchet@abes.fr</a> </pre> </body> </html> --------------050806000807090207010701--
This is a multi-part message in MIME format. --------------060009080107030600040909 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit - selecting the 'enable gluster service' in later stage(after the hosts are added) doesn't do anything. As you said, this could be a nice feature though. - 'gluster peer probe' is used to form a logical cluster. I don't think having the hosts from different clusters to form a gluster-cluster is the right way. Thanks, Kanagaraj On 06/02/2014 04:54 PM, Nathanaël Blanchet wrote:
Hi all,
I created 3 clusters in unique datacenter. I installed my hosts to the first one after activating the gluster service in the cluster tab. A expected otopi installed then the vdsm-gluster rpm and everything were ok for this first cluster. The other ones weren't initially gluster ready and I wanted to activate the service after installing the host (so they were without vdsm-gluster package). But checking that item didn't do anything for these hosts, so that I had to manually install vdsm-gluster package. Then, when creating a volume, the UI told me that hosts couldn't communicate. So I had to manually probe them. This leads me to that question : is it an expected behaviour? The whole gluster job (installing appropriated package and probing peers in the cluster) should be done thanks to the UI cluster tab "gluster service". A last question : why isn't it possible to probe host on different clusters in the same datacenter, could be very useful. -- Nathanaël Blanchet
Supervision réseau Pôle exploitation et maintenance Département des systèmes d'information 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet@abes.fr
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--------------060009080107030600040909 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> - selecting the 'enable gluster service' in later stage(after the hosts are added) doesn't do anything. As you said, this could be a nice feature though.<br> - 'gluster peer probe' is used to form a logical cluster. I don't think having the hosts from different clusters to form a gluster-cluster is the right way.<br> <br> Thanks,<br> Kanagaraj<br> <br> <div class="moz-cite-prefix">On 06/02/2014 04:54 PM, Nathanaël Blanchet wrote:<br> </div> <blockquote cite="mid:538C5EE3.1000808@abes.fr" type="cite"> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> <font size="-1">Hi all,<br> <br> I created 3 clusters in unique datacenter. I installed </font><font size="-1"><font size="-1">my hosts </font>to the first one after activating the gluster service in the cluster tab. A expected otopi installed then the vdsm-gluster rpm and everything were ok for this first cluster. <br> The other ones weren't initially gluster ready and I wanted to activate the service after installing the host (so they were without vdsm-gluster package). But checking that item didn't do anything for these hosts, so that I had to manually install vdsm-gluster package. Then, when creating a volume, the UI told me that hosts couldn't communicate. So I had to manually probe them. This leads me to that question : is it an expected behaviour? The whole gluster job (installing appropriated package and probing peers in the cluster) should be done thanks to the UI cluster tab "gluster service".<br> A last question : why isn't it possible to probe host on different clusters in the same datacenter, could be very useful.<br> </font> <pre class="moz-signature" cols="72">-- Nathanaël Blanchet Supervision réseau Pôle exploitation et maintenance Département des systèmes d'information 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:blanchet@abes.fr">blanchet@abes.fr</a> </pre> <br> <fieldset class="mimeAttachmentHeader"></fieldset> <br> <pre wrap="">_______________________________________________ Users mailing list <a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a> <a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a> </pre> </blockquote> <br> </body> </html> --------------060009080107030600040909--
Hi all,
I created 3 clusters in unique datacenter. I installed my hosts to the first one after activating the gluster service in the cluster tab. A expected otopi installed then the vdsm-gluster rpm and everything were ok for this first cluster. The other ones weren't initially gluster ready and I wanted to activate the service after installing the host (so they were without vdsm-gluster package). But checking that item didn't do anything for these hosts, so that I had to manually install vdsm-gluster package. Then, when creating a volume, the UI told me that hosts couldn't communicate. So I had to manually probe them. This leads me to that question : is it an expected behaviour? The whole gluster job (installing appropriated package and probing peers in the cluster) should be done thanks to the UI cluster tab "gluster service". A last question : why isn't it possible to probe host on different clusters in the same datacenter, could be very useful. After checking the checkbox for gluster services you'll need to migrated all vms from a host and put it into maintenance then use the re-install
This is a multi-part message in MIME format. --------------020202010309000408030402 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Nathanaël Blanchet wrote: link and the needed packages will be downloaded and installed and a peer probe will be done. After that reactivate the host and proceed to the next one. One caveat found: chkconfig glusterd on isn't executed. You'll need to do that by hand and also start the service or restart the server while in maintenance mode. Joop --------------020202010309000408030402 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Nathanaël Blanchet wrote: <blockquote cite="mid:538C5EE3.1000808@abes.fr" type="cite"> <meta http-equiv="content-type" content="text/html; "> <font size="-1">Hi all,<br> <br> I created 3 clusters in unique datacenter. I installed </font><font size="-1"><font size="-1">my hosts </font>to the first one after activating the gluster service in the cluster tab. A expected otopi installed then the vdsm-gluster rpm and everything were ok for this first cluster. <br> The other ones weren't initially gluster ready and I wanted to activate the service after installing the host (so they were without vdsm-gluster package). But checking that item didn't do anything for these hosts, so that I had to manually install vdsm-gluster package. Then, when creating a volume, the UI told me that hosts couldn't communicate. So I had to manually probe them. This leads me to that question : is it an expected behaviour? The whole gluster job (installing appropriated package and probing peers in the cluster) should be done thanks to the UI cluster tab "gluster service".<br> A last question : why isn't it possible to probe host on different clusters in the same datacenter, could be very useful.<br> </font></blockquote> After checking the checkbox for gluster services you'll need to migrated all vms from a host and put it into maintenance then use the re-install link and the needed packages will be downloaded and installed and a peer probe will be done. After that reactivate the host and proceed to the next one. One caveat found: chkconfig glusterd on isn't executed. You'll need to do that by hand and also start the service or restart the server while in maintenance mode.<br> <br> Joop<br> <br> </body> </html> --------------020202010309000408030402--
participants (3)
-
Joop -
Kanagaraj -
Nathanaël Blanchet