[RFE] Dynamically allocate console port

Bug #1526371 reported by Vladyslav Drok on 2015-12-15
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ironic
In Progress
Wishlist
Zhenguo Niu

Bug Description

Currently the way to enable console is to specify a terminal_port parameter, then if start console, shellinabox/socat will run with the terminal_port. there could be some nodes with same port number in a conductor server, so only one console can be enabled, and if the node is taken over by another conductor, the port may also be used by another shellinabox/socat service in that server. This is unacceptable, so I suggest to add a mechanism to manage the console port instead of specified by users.

Vladyslav Drok (vdrok) on 2015-12-15
Changed in ironic:
status: New → Confirmed
importance: Undecided → Wishlist
tags: added: rfe
Changed in ironic:
assignee: nobody → Zhenguo Niu (niu-zglinux)
status: Confirmed → In Progress
summary: - [RFE] Manage shellinabox console port
+ [RFE] Dynamically allocate shellinabox console port

Change abandoned by Zhenguo Niu (<email address hidden>) on branch: master
Review: https://review.openstack.org/258915
Reason: move to https://review.openstack.org/#/c/257789/

Zhenguo Niu (niu-zglinux) wrote :

update description to not only specify to shellinabox but also the new introduced console driver socat

summary: - [RFE] Dynamically allocate shellinabox console port
+ [RFE] Dynamically allocate console port
description: updated
tags: added: needs-spec
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related blueprints