I was able to use the brick reset process to change hostnames of all
gluster volumes. Traffic is now flowing through my 10gig gluster network.
Thanks for the assistance with this all!
On Thu, Oct 17, 2019 at 2:42 PM Strahil wrote:
> For example my gluster network IP is 10.10.10.1/24 and the
For example my gluster network IP is 10.10.10.1/24 and the /etc/hosts entry is:
10.10.10.1 gluster1.localdomain gluster1
Then I did 'gluster volume replace-brick ovirt1:/gluster_bricks/data/data
gluster1:/gluster_bricks/data/data commit'
So you use a hostname that is resolved either by DNS or
Sahina,
Thank you very much for the explanation. I definitely do want Gluster
traffic on my 10gig network but am being extra cautious because there are
live VMs on the volumes.
This is my current configuration
host0.blah.example.com: 10.11.0.220 (gluster interface: 10.12.0.220)
On Thu, Oct 17, 2019 at 7:22 PM Jayme wrote:
> Thanks for the info, but where does it get the new hostname from? Do I
> need to change the actual server hostnames of my nodes? If I were to do
> that then the hosts would not be accessible due to the fact that the
> gluster storage subnet is
Thanks for the info, but where does it get the new hostname from? Do I
need to change the actual server hostnames of my nodes? If I were to do
that then the hosts would not be accessible due to the fact that the
gluster storage subnet is isolated.
I guess I'm confused about what gdeploy does
The reset-brick and replace-brick affects only one brick and notifies the
gluster cluster that a new hostname:/brick_path is being used.
Of course, you need a hostname that resolves to the IP that is on the storage
network.
WARNING: Ensure that no heals are pending as the commands are wiping
On Wed, Oct 16, 2019 at 8:38 PM Jayme wrote:
> Is there a way to fix this on a hci deployment which is already in
> operation? I do have a separate gluster network which is chosen for
> migration and gluster network but when I originally deployed I used just
> one set of host names which
I had originally setup my cluster following this older guide at
https://blogs.ovirt.org/2018/02/up-and-running-with-ovirt-4-2-and-gluster-storage/
and
the fqdn steps did not exist at that time. After deployment I then followed
steps to add gluster network and set that network as storage and
Is there a way to fix this on a hci deployment which is already in
operation? I do have a separate gluster network which is chosen for
migration and gluster network but when I originally deployed I used just
one set of host names which resolve to management network subnet.
I appear to have a
Thank you Simone for the clarifications.
I've redeployed with both management and storage FQDNs; now everything seems to
be in its place.
I only have a couple of questions:
1) In the Gluster deployment Wizard, section 1 (Hosts) and 2 (Additional Hosts)
are misleading; should be renamed in
This is an interesting topic, I've had a 3 node HCI cluster configured the
same way and now I'm questioning whether or not my gluster traffic has been
using my gig network instead of my 10gig network on separate subnet.
On Wed, Oct 16, 2019 at 10:08 AM Simone Tiraboschi
wrote:
>
>
> On Wed, Oct
On Wed, Oct 16, 2019 at 2:16 PM Stefano Stagnaro <
stefa...@prismatelecomtesting.com> wrote:
> Hi,
>
> I've deployed an oVirt HC starting with latest oVirt Node 4.3.6; this is
> my simple network plan (FQDNs only resolves the front-end addresses):
>
> front-end
12 matches
Mail list logo
