Bug 1073531 - gluster service should be enabled by default
Summary: gluster service should be enabled by default
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-node-plugin-vdsm
Version: 3.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.4.1
Assignee: Douglas Schilling Landgraf
QA Contact: Pavel Stehlik
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-06 15:50 UTC by Fabian Deutsch
Modified: 2014-04-04 01:50 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-04-04 01:50:29 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 26203 0 master MERGED spec: start/enable glusterd Never

Description Fabian Deutsch 2014-03-06 15:50:22 UTC
Description of problem:
glusterd is not started by default.
The plugin should enable glusterd by default so it can be used.

Comment 1 Fabian Deutsch 2014-03-06 16:33:11 UTC
Shai, it wuold be great if someone could test gluster storage with ovirt-node-iso.

Comment 2 Fabian Deutsch 2014-04-02 07:38:56 UTC
Hey,

I believe I did not make this clear enough initially.

The user mentioning this problem tried to setup a "gluster cluster".
As I am not aware of how this works, I just assumed that the same vdsm could be used for virt and gluster clusters.

But maybe someone can explain to me if the same vdsm can be used for gluster and virt at the same time?

And if not - how we want to also allow gluster Nodes.

Douglas, sorry for not making this clear initially.

Comment 3 Ryan Barry 2014-04-02 14:15:52 UTC
ovirt-node-plugin-vdsm pulls in vdsm-gluster anyway, and it's able to manage it. As long as we add glusterfs-server (or glusterfs, depending on what distro), VDSM can manage it as long as the ports are open and the service is started, from my testing.

Comment 4 Douglas Schilling Landgraf 2014-04-04 01:50:29 UTC
Hi Fabian,

As we talked this should be managed outside of ovirt-node-plugin-vdsm, based on cluster level. Closing this bug for now.


Note You need to log in before you can comment on or make changes to this bug.