Bug 1142705 - [RFE]Option to specify a keyfile needed for Geo-replication create push-pem command.
Summary: [RFE]Option to specify a keyfile needed for Geo-replication create push-pem c...
Keywords:
Status: CLOSED DUPLICATE of bug 1136296
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: mainline
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Ajeet Jha
QA Contact:
URL:
Whiteboard:
Depends On: 1136296 1139105
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-17 08:55 UTC by Aravinda VK
Modified: 2015-02-22 23:01 UTC (History)
10 users (show)

Fixed In Version:
Clone Of: 1139105
Environment:
Last Closed: 2014-09-17 09:04:33 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Aravinda VK 2014-09-17 08:55:58 UTC
+++ This bug was initially created as a clone of Bug #1139105 +++

+++ This bug was initially created as a clone of Bug #1136296 +++

Description of problem: 

    Currently geo-replication needs password-less ssh to be set up using the default key "~/.ssh/id_rsa" located at root users home directory. It should be possible to create password-less ssh using other keyfile, and an option to geo-replication create push-pem command to specify this keyfile. Geo-replication must use this key for further operations. 

    When setting geo-replication through RHSC, if the key file  "~/.ssh/id_rsa"  is not present . We will have to generate the key and use it. But since the location of keyfile is root users home directory. If root user runs ssh-keygen or deletes the keyfile at a later point of time the keyfile used for geo-replication will be gone and geo-replication stops functioning. So if we can specify a keyfile to geo-replication, we can have the keyfile stored in a safe location where it is not easily meddled by users. 

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from RHEL Product and Program Management on 2014-09-08 01:22:22 EDT ---

Since this issue was entered in bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 1 Aravinda VK 2014-09-17 09:04:33 UTC

*** This bug has been marked as a duplicate of bug 1136296 ***


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