Bug 1085901 - [RFE] ovirt-node: Security tab (users must be able to choose the ssh daemon port)
Summary: [RFE] ovirt-node: Security tab (users must be able to choose the ssh daemon p...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-node
Version: 3.4.0
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: ---
Assignee: Ryan Barry
QA Contact: Virtualization Bugs
URL:
Whiteboard: node
Depends On: 1085907
Blocks: 1123945
TreeView+ depends on / blocked
 
Reported: 2014-04-09 15:27 UTC by Douglas Schilling Landgraf
Modified: 2019-04-28 10:49 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-23 10:22:35 UTC
oVirt Team: Node
Target Upstream Version:
Embargoed:
sherold: Triaged+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 26631 0 master ABANDONED Allow users to choose the SSH port Never

Description Douglas Schilling Landgraf 2014-04-09 15:27:12 UTC
Description of problem:

If users want to use a different ssh port to communicate between ovirt-node and ovirt-engine we should be able to configure it via TUI on ovirt-node.

My suggestion is on ovirt-node in Security tab have an option for it.

[ 22 ] SSH Daemon Port (or something like)

When users provide the ssh port we need also to setup the firewall rules for this new port.

Comment 1 Fabian Deutsch 2014-06-19 07:57:39 UTC
The patch is actually 92d26a1369cd4b3dcd59217f7e4c1b0f743a22c0

Comment 7 Fabian Deutsch 2014-08-11 12:45:30 UTC
Moving this into the future, as the Engine side part is missing.

Comment 9 Doron Fediuck 2014-08-24 14:09:26 UTC
Marking as 3.5.0 since the node part is ready and can be tested for
basic ssh connectivity using a different port than 22. However, to get the
feature working with the engine Bug 1085907 should be completed. In the meantime
the node part is ready.

Comment 10 Fabian Deutsch 2014-09-01 10:23:40 UTC
For now the feature is hidden from the users eyes (by hiding the appropriate box in the TUI).

The reason is to prevent any accidental change of the port, which will result in the loss of communication between Node and Engine.

This also means that this feature can currently not be tested.

Comment 11 Fabian Deutsch 2014-09-01 19:00:15 UTC
Moving this bug to 3.6, because it can currently not be tested.


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