Hey Shareef,
if you have slow ssh login - check the A/AAAA & PTR records of both ssh client.
By default ssh is checking the PTR record of the client and this can take some time to
timeout (and reach a good dns or fail).
Also, you could have issues with 7.3 systems - as systemd is not cleaning up properly
orphaned session/scope files. There is an RedHat Solution that almost work :)
Best Regards,
Strahil Nikolov
В сряда, 29 април 2020 г., 00:50:14 Гринуич+3, Jayme <jaymef(a)gmail.com> написа:
You should use host names for gluster like
gluster1.hostname.com that resolve to the ip
chosen for gluster.
For my env I have something like this:
Server0:
Host0.example.com 10.10.0.100
Gluster0.example.com 10.0.1.100
Same thing for other two severs except hostnames and ips of course.
Use the gluster hostnames for the first step then the sever hostnames for the others.
I made sure I could ssh to and from both hostX and glusterX on each server.
On Tue, Apr 28, 2020 at 6:34 PM Shareef Jalloq <shareef(a)jalloq.co.uk> wrote:
Perhaps it's me, but these two documents seem to disagree on what
hostnames to use when setting up. Can someone clarify.
The main documentation
here: https://www.ovirt.org/documentation/gluster-hyperconverged/chap-Dep...
about copying the SSH keys to the gluster host address but the old blog post with an
outdated interface
here: https://blogs.ovirt.org/2018/02/up-and-running-with-ovirt-4-2-and-g...
the node address.
In the first step of the hyperconverged Gluster wizard, when it asks for "Gluster
network address", is this wanting the host IP or the IP of the Gluster interface?
On Tue, Apr 28, 2020 at 10:24 PM Shareef Jalloq <shareef(a)jalloq.co.uk> wrote:
> OK, thanks both, that seems to have fixed that issue.
>
> Is there any other config I need to do because the next step in the deployment guide
of copying SSH keys seems to take over a minute just to prompt for a password. Something
smells here.
>
> On Tue, Apr 28, 2020 at 7:32 PM Jayme <jaymef(a)gmail.com> wrote:
>> You should be using a different subnet for each. I.e. 10.0.0.30 and 10.0.1.30 for
example
>>
>> On Tue, Apr 28, 2020 at 2:49 PM Shareef Jalloq <shareef(a)jalloq.co.uk>
wrote:
>>> Hi,
>>>
>>> I'm in the process of trying to set up an HCI 3 node cluster in my
homelab to better understand the Gluster setup and have failed at the first hurdle.
I've set up the node interfaces on the built in NIC and am using a PCI NIC for the
Gluster traffic - at the moment this is 1Gb until I can upgrade - and I've assigned a
static IP to both interfaces and also have both entries in my DNS.
>>>
>>> From any of the three nodes, I can ping the gateway, the other nodes, any
external IP but I can't ping any of the Gluster NICs. What have I forgotten to do?
Here's the relevant output of 'ip addr show'. em1 is the motherboard NIC and
p1p1 is port 1 of an Intel NIC. The /etc/sysconfig/network-scripts/ifcfg-<if>
scripts are identical aside from IPADDR, NAME, DEVICE and UUID fields.
>>>
>>> Thanks, Shareef.
>>>
>>>
>>> [root@ovirt-node-00 ~]# ip addr show
>>>
>>>
>>>
>>> 2: p1p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
group default qlen 1000
>>>
>>> link/ether a0:36:9f:1f:f9:78 brd ff:ff:ff:ff:ff:ff
>>>
>>> inet 10.0.0.34/24 brd 10.0.0.255 scope global noprefixroute p1p1
>>>
>>> valid_lft forever preferred_lft forever
>>>
>>> inet6 fd4d:e9e3:6f5:1:a236:9fff:fe1f:f978/64 scope global mngtmpaddr
dynamic
>>>
>>> valid_lft 7054sec preferred_lft 7054sec
>>>
>>> inet6 fe80::a236:9fff:fe1f:f978/64 scope link
>>>
>>> valid_lft forever preferred_lft forever
>>>
>>>
>>>
>>> 4: em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP group default qlen 1000
>>>
>>> link/ether 98:90:96:a1:16:ad brd ff:ff:ff:ff:ff:ff
>>>
>>> inet 10.0.0.31/24 brd 10.0.0.255 scope global noprefixroute em1
>>>
>>> valid_lft forever preferred_lft forever
>>>
>>> inet6 fd4d:e9e3:6f5:1:9a90:96ff:fea1:16ad/64 scope global mngtmpaddr
dynamic
>>>
>>> valid_lft 7054sec preferred_lft 7054sec
>>>
>>> inet6 fe80::9a90:96ff:fea1:16ad/64 scope link
>>>
>>> valid_lft forever preferred_lft forever
>>>
>>>
>>> _______________________________________________
>>> 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/S7UESGZ6MJX...
>>>
>>
>
_______________________________________________
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/KVMZSD7YPPS...