Bug 1049994

Summary:	[RFE][HC] - Allow choosing network interface for gluster domain traffic
Product:	[oVirt] ovirt-engine	Reporter:	Juan Pablo Lorier <jplorier>
Component:	RFEs	Assignee:	Sahina Bose <sabose>
Status:	CLOSED CURRENTRELEASE	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	high
Version:	---	CC:	bugs, gklein, iheim, info, jplorier, lpeer, mgoldboi, oourfali, rbalakri, sabose, s.kieske, yeylon, ykaul, ylavi
Target Milestone:	ovirt-3.6.0-rc	Keywords:	FutureFeature
Target Release:	3.6.0	Flags:	rule-engine: ovirt-3.6.0+ ylavi: planning_ack+ rule-engine: devel_ack+ rule-engine: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-3.6.0-0.0.master.20150515172356.git426b5a1	Doc Type:	Enhancement
Doc Text:	Feature: Add all interfaces of hosts in a glusterfs cluster for been able to choose which use for gluster traffic Reason: Not allowing to choose which interface of the bricks to use causes the bricks to use a no optimal interface for gluster traffic and causes errors in host monitoring by engine. Result (if any): Better utilization of network resources.	Story Points:	---
Clone Of:
Clones:	1224281 (view as bug list)		Environment:
Last Closed:	2016-03-11 07:19:31 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Gluster	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1057450, 1177771, 1187461, 1193999, 1224281, 1277939

Description Juan Pablo Lorier 2014-01-08 15:23:13 UTC

Description of problem:

When creating a new gluster volume the default interface used for gluster traffic is the ovirtmgmt though threre are other interfaces available. This causes network saturation.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.Create a new gluster volume in a glusterfs domain
2.you can choose only the ovirtmgmt ip from the drop down menu when adding bricks
3.

Actual results:
Only ovirtmgmt interface is used for gluster traffic creating a bottleneck and render hosts unreachable during heavy disk workloads (like importing a vm)

Expected results:
Been able to choose among all interfaces of the hosts.

Additional info:

Comment 1 Juan Pablo Lorier 2014-01-08 15:42:29 UTC

One more thing is that this is causing the cluster to be unusable as it keeps bringing hosts down in engine when I try to import a vm (it uses a lot of bandwith). There's a way to change this after the volume is created by using gluster commands, but I think it should be done straight at creation time within webadmin and else, have the posibility of changing it after the volume is active (someone could get new interfaces after having the volume in production).

.

Comment 2 Yaniv Lavi 2014-12-30 12:02:40 UTC

*** Bug 1177778 has been marked as a duplicate of this bug. ***

Comment 3 Yaniv Lavi 2015-04-08 07:56:36 UTC

Should this be on MODIFIED?

Comment 4 SATHEESARAN 2016-03-08 08:49:56 UTC

Tested with  3.6.3.4-1.el7.centos + gluster 3.7.5

Following are the observations,
1. I could create a separate logical network for gluster
2. I could assign a role gluster for that network
3. Volume created use this network

Based on the above marking this bug as verified