Activity log for bug #1526371

Date Who What changed Old value New value Message
2015-12-15 15:08:29 Vladyslav Drok bug added bug
2015-12-15 15:08:34 Vladyslav Drok ironic: status New Confirmed
2015-12-15 15:08:36 Vladyslav Drok ironic: importance Undecided Wishlist
2015-12-15 15:08:39 Vladyslav Drok tags rfe
2015-12-16 07:25:08 OpenStack Infra ironic: status Confirmed In Progress
2015-12-16 07:25:08 OpenStack Infra ironic: assignee Zhenguo Niu (niu-zglinux)
2016-01-28 20:42:57 Vladyslav Drok removed subscriber Vladyslav Drok
2016-02-03 03:17:08 Zhenguo Niu summary [RFE] Manage shellinabox console port [RFE] Dynamically allocate shellinabox console port
2016-07-22 07:07:32 Zhenguo Niu summary [RFE] Dynamically allocate shellinabox console port [RFE] Dynamically allocate console port
2016-07-22 07:08:05 Zhenguo Niu description Currently the way to enable console is to specify a terminal_port parameter, then if start console, shellinabox 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 service in that server. This is unacceptable, so I suggest to add a mechanism to manage the console port instead of specified by users. 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.
2016-09-14 15:17:35 Jim Rollenhagen tags rfe needs-spec rfe
2018-04-11 11:46:10 Uemit Seren bug added subscriber Uemit Seren