1:10 a.m.
This is a multi-part message in MIME format.
--------------5AF6806598CC27E8D12E46F0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
On 08/22/2016 11:24 AM, Sahina Bose wrote:
On Fri, Aug 19, 2016 at 6:20 PM, Nicolas Ecarnot <nicolas(a)ecarnot.net
<mailto:nicolas@ecarnot.net>> wrote:
Le 19/08/2016 à 13:43, Sahina Bose a écrit :
>
>> Or are you adding the 3 nodes to your existing cluster? If
>> so, I suggest you try adding this to a new cluster
> OK, I tried and succeed to create a new cluster.
> In this new cluster, I was ABLE to add the first new host,
> using its mgmt DNS name.
> This first host still has to have its NICs configured, and
> (using Chrome or FF) the access to the network settings
> window is stalling the browser (I tried to restart even the
> engine, to no avail). Thus, I can not setup this first node NICs.
>
> Thus, I can not add any further host because oVirt relies on
> a first host to validate the further ones.
>
>
>
> Network team should be able to help you here.
>
OK, there were no mean I could continue this way (browser crash),
so I tried and succeed doing so :
- remove the newly created host and cluster
- create a new DATACENTER
- create a new cluster in this DC
- add the first new host : OK
- add the 2 other new hosts : OK
Now, I can smoothly configure their NICs.
Doing all this, I saw that oVirt detected there already was
existing gluster cluster and volume, and integrated it in oVirt.
Then, I was able to create a new storage domain in this new DC and
cluster, using one of the *gluster* FQDN's host. It went nicely.
BUT, when viewing the volume tab and brick details, the displayed
brick names are the host DNS name, and NOT the host GLUSTER DNS names.
I'm worrying about this, confirmed by what I read in the logs :
2016-08-19 14:46:30,484 WARN
[org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturnForXmlRpc]
(DefaultQuartzScheduler_Worker-100) [107dc2e3] Could not associate
brick 'serv-vm-al04-data.sdis.isere.fr:/gluster/data/brick04
' of volume '35026521-e76e-4774-8ddf-0a701b9eb40c' with correct
network as no gluster network found in cluster
'1c8e75a0-af3f-4e97-a8fb-2f7ef3ed9f30'
2016-08-19 14:46:30,492 WARN
[org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturnForXmlRpc]
(DefaultQuartzScheduler_Worker-100) [107dc2e3] Could not associate
brick 'serv-vm-al05-data.sdis.isere.fr:/gluster/data/brick04
' of volume '35026521-e76e-4774-8ddf-0a701b9eb40c' with correct
network as no gluster network found in cluster
'1c8e75a0-af3f-4e97-a8fb-2f7ef3ed9f30'
2016-08-19 14:46:30,500 WARN
[org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturnForXmlRpc]
(DefaultQuartzScheduler_Worker-100) [107dc2e3] Could not associate
brick 'serv-vm-al06-data.sdis.isere.fr:/gluster/data/brick04
' of volume '35026521-e76e-4774-8ddf-0a701b9eb40c' with correct
network as no gluster network found in cluster
'1c8e75a0-af3f-4e97-a8fb-2f7ef3ed9f30'
[oVirt shell (connected)]# list clusters
id : 00000001-0001-0001-0001-000000000045
name : cluster51
description: Cluster d'alerte de test
id : 1c8e75a0-af3f-4e97-a8fb-2f7ef3ed9f30
name : cluster52
description: Cluster d'alerte de test
[oVirt shell (connected)]#
"cluster52" is the recent cluster, and I do have a dedicated
gluster network, marked as gluster network, in the correct DC and
cluster.
The only point is that :
- Each host has its name ("serv-vm-al04") and a second name for
gluster ("serv-vm-al04-data").
- Using blahblahblah-data is correct on a gluster point of view
- Maybe oVirt is disturb not to be able to ping the gluster FQDN
(not routed) and then throwing this error?
We do have a limitation currently that if you use multiple FQDNs,
oVirt cannot associate it to the gluster brick correctly. This will be
a problem only when you try brick management from oVirt - i.e try to
remove or replace brick from oVirt. For monitoring brick status and
detecting bricks - this is not an issue, and you can ignore the error
in logs.
Adding Ramesh who has a patch to fix this .
Patch https://gerrit.ovirt.org/#/c/60083/ is posted to address this
issue. But it will work only if the oVirt Engine can resolve FQDN
*'serv-vm-al04-data.xx*'* to an IP address which is mapped to the
gluster NIC (NIC with gluster network) on the host.
Sahina: Can you review the patch :-)
Regards,
Ramesh
--
Nicolas ECARNOT
--------------5AF6806598CC27E8D12E46F0
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 08/22/2016 11:24 AM, Sahina Bose
wrote:<br>
</div>
<blockquote
cite="mid:CACjzOvfM4kju4oWrpw2Lxbc7Kf3-OU8J2ErkxrgBKmcYEZEh6Q@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Aug 19, 2016 at 6:20 PM,
Nicolas Ecarnot <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:nicolas@ecarnot.net"
target="_blank"><a
class="moz-txt-link-abbreviated"
href="mailto:nicolas@ecarnot.net">nicolas@ecarnot.net</a></a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><span
class="">
<div>Le 19/08/2016 à 13:43, Sahina Bose a écrit :<br>
</div>
<blockquote type="cite">
<div dir="ltr"><span></span><br>
<span> </span>
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote"
style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF"
text="#000000"><span>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div> Or are you adding the 3
nodes to your existing
cluster? If so, I suggest you
try adding this to a new
cluster<br>
</div>
</div>
</div>
</div>
</blockquote>
</span> OK, I tried and succeed to create
a new cluster.<br>
In this new cluster, I was ABLE to add the
first new host, using its mgmt DNS name.<br>
This first host still has to have its NICs
configured, and (using Chrome or FF) the
access to the network settings window is
stalling the browser (I tried to restart
even the engine, to no avail). Thus, I can
not setup this first node NICs.<br>
<br>
Thus, I can not add any further host
because oVirt relies on a first host to
validate the further ones.<span><font
color="#888888"><br>
</font></span></div>
</blockquote>
<div><br>
<br>
</div>
<div>Network team should be able to help you
here.<br>
</div>
</div>
<br>
</div>
</div>
</blockquote>
<br>
</span> OK, there were no mean I could continue this way
(browser crash), so I tried and succeed doing so :<br>
- remove the newly created host and cluster<br>
- create a new DATACENTER<br>
- create a new cluster in this DC<br>
- add the first new host : OK<br>
- add the 2 other new hosts : OK<br>
<br>
Now, I can smoothly configure their NICs.<br>
<br>
Doing all this, I saw that oVirt detected there already
was existing gluster cluster and volume, and integrated
it in oVirt.<br>
<br>
Then, I was able to create a new storage domain in this
new DC and cluster, using one of the *gluster* FQDN's
host. It went nicely.<br>
<br>
BUT, when viewing the volume tab and brick details, the
displayed brick names are the host DNS name, and NOT the
host GLUSTER DNS names.<br>
<br>
I'm worrying about this, confirmed by what I read in the
logs :<br>
<br>
2016-08-19 14:46:30,484 WARN
[org.ovirt.engine.core.<wbr>vdsbroker.gluster.<wbr>GlusterVolumesListReturnForXml<wbr>Rpc]
(DefaultQuartzScheduler_<wbr>Worker-100) [107dc2e3]
Could not associate brick
'serv-vm-al04-data.sdis.isere.<wbr>fr:/gluster/data/brick04<br>
' of volume '35026521-e76e-4774-8ddf-<wbr>0a701b9eb40c'
with correct network as no gluster network found in
cluster
'1c8e75a0-af3f-4e97-a8fb-<wbr>2f7ef3ed9f30'<br>
2016-08-19 14:46:30,492 WARN
[org.ovirt.engine.core.<wbr>vdsbroker.gluster.<wbr>GlusterVolumesListReturnForXml<wbr>Rpc]
(DefaultQuartzScheduler_<wbr>Worker-100) [107dc2e3]
Could not associate brick
'serv-vm-al05-data.sdis.isere.<wbr>fr:/gluster/data/brick04<br>
' of volume '35026521-e76e-4774-8ddf-<wbr>0a701b9eb40c'
with correct network as no gluster network found in
cluster
'1c8e75a0-af3f-4e97-a8fb-<wbr>2f7ef3ed9f30'<br>
2016-08-19 14:46:30,500 WARN
[org.ovirt.engine.core.<wbr>vdsbroker.gluster.<wbr>GlusterVolumesListReturnForXml<wbr>Rpc]
(DefaultQuartzScheduler_<wbr>Worker-100) [107dc2e3]
Could not associate brick
'serv-vm-al06-data.sdis.isere.<wbr>fr:/gluster/data/brick04<br>
' of volume '35026521-e76e-4774-8ddf-<wbr>0a701b9eb40c'
with correct network as no gluster network found in
cluster
'1c8e75a0-af3f-4e97-a8fb-<wbr>2f7ef3ed9f30'<br>
<br>
[oVirt shell (connected)]# list clusters<br>
<br>
id : 00000001-0001-0001-0001-<wbr>000000000045<br>
name : cluster51<br>
description: Cluster d'alerte de test<br>
<br>
id : 1c8e75a0-af3f-4e97-a8fb-<wbr>2f7ef3ed9f30<br>
name : cluster52<br>
description: Cluster d'alerte de test<br>
<br>
[oVirt shell (connected)]# <br>
<br>
"cluster52" is the recent cluster, and I do have a
dedicated gluster network, marked as gluster network, in
the correct DC and cluster.<br>
The only point is that :<br>
- Each host has its name ("serv-vm-al04") and a second
name for gluster ("serv-vm-al04-data").<br>
- Using blahblahblah-data is correct on a gluster point
of view<br>
- Maybe oVirt is disturb not to be able to ping the
gluster FQDN (not routed) and then throwing this error?<span
class="HOEnZb"><font
color="#888888"><br>
<br>
</font></span></div>
</blockquote>
<div><br>
</div>
<div>We do have a limitation currently that if you use
multiple FQDNs, oVirt cannot associate it to the gluster
brick correctly. This will be a problem only when you try
brick management from oVirt - i.e try to remove or replace
brick from oVirt. For monitoring brick status and
detecting bricks - this is not an issue, and you can
ignore the error in logs.<br>
<br>
</div>
<div>Adding Ramesh who has a patch to fix this .<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
Patch <a
href="https://gerrit.ovirt.org/#/c/60083/">https://gerrit.ov...
is posted to address this issue. But it will work only if the oVirt
Engine can resolve FQDN <b>'serv-vm-al04-data.xx*'</b> to an IP
address which is mapped to the gluster NIC (NIC with gluster
network) on the host.<br>
<br>
Sahina: Can you review the patch :-)<br>
<br>
Regards,<br>
Ramesh<br>
<br>
<div bgcolor="#FFFFFF"
text="#000000"><wbr></div>
<blockquote
cite="mid:CACjzOvfM4kju4oWrpw2Lxbc7Kf3-OU8J2ErkxrgBKmcYEZEh6Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><span
class="HOEnZb"><font
color="#888888"> -- <br>
Nicolas ECARNOT<br>
</font></span></div>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
<br>
</body>
</html>
--------------5AF6806598CC27E8D12E46F0--