Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Ganesha HA bits back to glusterfs code repo #663

Closed
thotz opened this issue Apr 26, 2019 · 6 comments
Closed

Add Ganesha HA bits back to glusterfs code repo #663

thotz opened this issue Apr 26, 2019 · 6 comments
Assignees
Labels
Type:Bug wontfix Managed by stale[bot]
Milestone

Comments

@thotz
Copy link
Contributor

thotz commented Apr 26, 2019

Till 3.12, glusterd had an option to setup HA cluster for nfs-ganesha using pacemaker and corosync infavour of "Storhaug" Project. But it also becomes in a halt state. Since there is not much development towards storhaug, it better to keep back old working HA solution for nfs-ganesha with bit improvements.

There were two old cli's for setting up and exporting the volume and helper script ganesha-ha.sh to manage ganesha cluster.
gluster nfs-ganesha enable/disable --> setting up/ teardown ganesha HA cluster
gluster v set ganesha.enable on/off --> [un/]exporting the volume
ganesha.sh options
--add -> add node to ganesha cluster
--delete -> delete node from ganesha cluster
--refresh-config -> modify the ganesha export
--status -> health check for ganesha cluster

Improvements

  • add options in nfs-ganesha enable command like
    gluster nfs-ganesha enable --no-ha, will start nfs-ganesha on all the nodes but won't set up ganesha HA cluster

  • Handling of export id's properly in the scripts
    current all of the scripts expects the volume configuration have single export id. But it is wrong for subdir exports. Planning to fix the same

@gluster-ant
Copy link
Collaborator

A patch https://review.gluster.org/22637 has been posted that references this issue.

Revert "glusterd: (storhaug) remove ganesha"

Change-Id: I811efefc148453fe32e4f0d322e80455447cec71
updates: #663
Signed-off-by: Jiffin Tony Thottan jthottan@redhat.com

@gluster-ant
Copy link
Collaborator

A patch https://review.gluster.org/22636 has been posted that references this issue.

Revert "packaging: (ganesha) remove glusterfs-ganesha subpackage and related files"

Change-Id: I1d60c8970bfc20035cf674d7b2705dfd4819647e
updates: #663
Signed-off-by: Jiffin Tony Thottan jthottan@redhat.com

gluster-ant pushed a commit that referenced this issue Aug 24, 2019
…related files"

Until 3.12, glusterd had an option to setup HA cluster for nfs-ganesha using pacemaker
and corosync. But later infavour of "Storhaug" Project, this functionality was removed
from the codebase. Since there is not much development happening towards storhaug,
it better to keep back old working HA solution for nfs-ganesha with bit improvements.

Planned improvements :

* add an option in nfs-ganesha enable to set ganesha without HA.

* Handle usage of export id's properly in the scripts.

Change-Id: I1d60c8970bfc20035cf674d7b2705dfd4819647e
updates: #663
Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
gluster-ant pushed a commit that referenced this issue Aug 24, 2019
please note as an additional change, macro GLUSTERD_GET_SNAP_DIR
moved from glusterd-store.c to glusterd-snapshot-utils.h

Change-Id: I811efefc148453fe32e4f0d322e80455447cec71
updates: #663
Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
@stale
Copy link

stale bot commented Apr 30, 2020

Thank you for your contributions.
Noticed that this issue is not having any activity in last ~6 months! We are marking this issue as stale because it has not had recent activity.
It will be closed in 2 weeks if no one responds with a comment here.

@stale stale bot added the wontfix Managed by stale[bot] label Apr 30, 2020
@thotz
Copy link
Contributor Author

thotz commented May 4, 2020

The change was merged upstream

@stale stale bot removed the wontfix Managed by stale[bot] label May 4, 2020
@stale
Copy link

stale bot commented Nov 30, 2020

Thank you for your contributions.
Noticed that this issue is not having any activity in last ~6 months! We are marking this issue as stale because it has not had recent activity.
It will be closed in 2 weeks if no one responds with a comment here.

@stale stale bot added the wontfix Managed by stale[bot] label Nov 30, 2020
@stale
Copy link

stale bot commented Dec 15, 2020

Closing this issue as there was no update since my last update on issue. If this is an issue which is still valid, feel free to open it.

@stale stale bot closed this as completed Dec 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type:Bug wontfix Managed by stale[bot]
Projects
None yet
Development

No branches or pull requests

4 participants