Bug 1292188 - [RFE] Gluster - Align new cluster dialog (import existing gluster) with add host
Summary: [RFE] Gluster - Align new cluster dialog (import existing gluster) with add host
Keywords:
Status: CLOSED DUPLICATE of bug 1164103
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Gluster
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.0.0-alpha
: ---
Assignee: Sahina Bose
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-16 16:59 UTC by Alon Bar-Lev
Modified: 2016-03-28 07:54 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-28 07:54:09 UTC
oVirt Team: Gluster
Embargoed:
ylavi: ovirt-4.0.0?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)

Description Alon Bar-Lev 2015-12-16 16:59:53 UTC
Currently only password authentication is available to authenticate to host, this is insecure, also there is no way to force a specific host public key, only fetch existing.

Dialog should:
1. present an option to view engine public key.
2. enable selection between password or public key authentication.
3. enable to paste host ssh public key fingerprint (or in near future host ssh public key), the fetch should be an optional operation.

Comment 1 Red Hat Bugzilla Rules Engine 2015-12-16 21:42:19 UTC
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Comment 2 Red Hat Bugzilla Rules Engine 2015-12-16 21:42:19 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 4 Yaniv Kaul 2016-03-28 07:54:09 UTC

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


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