Bug 1198615 - geo-replication create command must have an option to avoid slave verification.
Summary: geo-replication create command must have an option to avoid slave verification.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Darshan
QA Contact:
URL:
Whiteboard:
: 1198614 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-04 14:13 UTC by Darshan
Modified: 2015-05-14 17:35 UTC (History)
3 users (show)

Fixed In Version: glusterfs-3.7.0beta1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-05-14 17:26:51 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Darshan 2015-03-04 14:13:24 UTC
Description of problem:
geo-replication create command should have an option to avoid slave side verification like:

* if slave host is pingable
* has proper passwordless ssh login setup
* slave volume is created and is empty
* if slave has enough memory

This option is needed by ovirt-engine as the tasks done
by push-pem is taken care by ovirt-engine and also the
above checks are done. Thus creation of password-less
ssh is avoided when managing geo-replication through
ovirt.



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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Anand Avati 2015-03-04 14:40:52 UTC
REVIEW: http://review.gluster.org/9799 (geo-rep-cli: added a new option "no-verify" to geo-rep create.) posted (#1) for review on master by darshan n (dnarayan)

Comment 2 Anand Avati 2015-03-05 06:47:18 UTC
REVIEW: http://review.gluster.org/9799 (geo-rep-cli: added a new option "no-verify" to geo-rep create.) posted (#2) for review on master by darshan n (dnarayan)

Comment 3 Darshan 2015-03-10 12:57:26 UTC
*** Bug 1198614 has been marked as a duplicate of this bug. ***

Comment 4 Anand Avati 2015-03-12 07:11:12 UTC
REVIEW: http://review.gluster.org/9799 (geo-rep-cli: added a new option "no-verify" to geo-rep create.) posted (#3) for review on master by darshan n (dnarayan)

Comment 5 Anand Avati 2015-03-12 07:19:01 UTC
REVIEW: http://review.gluster.org/9799 (geo-rep-cli: added a new option "no-verify" to geo-rep create.) posted (#4) for review on master by darshan n (dnarayan)

Comment 6 Anand Avati 2015-03-13 06:34:28 UTC
COMMIT: http://review.gluster.org/9799 committed in master by Krishnan Parthasarathi (kparthas) 
------
commit 7c177bda6ccd1c3e7a7c070eb2ab0dc5e6b32a5c
Author: darshan n <dnarayan>
Date:   Wed Mar 4 19:18:10 2015 +0530

    geo-rep-cli: added a new option "no-verify" to geo-rep create.
    
    This patch adds a new option called as "no-verify" to geo-rep
    create command. With no-verify option, following checks does
    not take place before session creation:
    
    * if ssh port 22 is open in slave
    * has proper passwordless ssh login setup
    * slave volume is created and is empty
    * if slave has enough memory
    
    This option is needed by ovirt-engine as the tasks done
    by push-pem is taken care by ovirt-engine and also the
    above checks are done. Thus creation of password-less
    ssh can be avoided when geo-replication is managed
    through ovirt.
    
    Usage: volume geo-replication [<VOLNAME>] [<SLAVE-URL>]
           { create [[no-verify]|[push-pem]] [force]|
             start [force]|stop [force]|pause [force]|
             resume [force]|config|status [detail]|
             delete } [options...]
    
    Change-Id: I975265f27d6434be5409438257d09cd4190c9159
    BUG: 1198615
    Signed-off-by: darshan n <dnarayan>
    Reviewed-on: http://review.gluster.org/9799
    Reviewed-by: Aravinda VK <avishwan>
    Reviewed-by: Kotresh HR <khiremat>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas>
    Tested-by: Krishnan Parthasarathi <kparthas>

Comment 7 Niels de Vos 2015-05-14 17:26:51 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 8 Niels de Vos 2015-05-14 17:28:27 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 9 Niels de Vos 2015-05-14 17:35:16 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user


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