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--