Bug 1139105 - [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 NOTABUG
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: geo-replication
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: ---
Assignee: Nagaprasad Sathyanarayana
QA Contact: storage-qa-internal@redhat.com
URL:
Whiteboard:
Depends On: 1136296
Blocks: 1142705
TreeView+ depends on / blocked
 
Reported: 2014-09-08 05:21 UTC by Darshan
Modified: 2016-02-18 00:20 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of: 1136296
: 1142705 (view as bug list)
Environment:
Last Closed: 2015-03-31 06:30:07 UTC
Embargoed:


Attachments (Terms of Use)

Description Darshan 2014-09-08 05:21:53 UTC
+++ 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:


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