Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

list OpenSSH as pre-req #593

Closed
OnnoVdT opened this issue Jun 17, 2019 · 6 comments
Closed

list OpenSSH as pre-req #593

OnnoVdT opened this issue Jun 17, 2019 · 6 comments
Labels
area: docs Documentation issue or issues that have documentation impact area: misc This issue is a miscelleneous doc requirement not for a specific component or area

Comments

@OnnoVdT
Copy link
Contributor

OnnoVdT commented Jun 17, 2019

No description provided.

@OnnoVdT
Copy link
Contributor Author

OnnoVdT commented Jun 17, 2019

https://zowe.github.io/docs-site/latest/user-guide/systemrequirements.html lists z/OS, z/OSMF and Node as pre-req, but not OpenSSH. Like z/OSMF, OpenSSH was added to base z/OS in 2.2, but it is not configured by default. So the sysprog will have to take action if it's not set up already for another reason.

@nannanli nannanli added the area: docs Documentation issue or issues that have documentation impact label Jul 2, 2019
@nannanli
Copy link
Member

nannanli commented Jul 2, 2019

@Joe-Winchester @NayerNajafi Hi Joe, Nayer, any comment on this request to list OpenSSH as a pre-req for Zowe? Thanks!

@nannanli nannanli added the area: misc This issue is a miscelleneous doc requirement not for a specific component or area label Jul 2, 2019
@Joe-Winchester
Copy link
Member

@OnnoVdT - good catch. I wasn't aware that OpenSSH wasn't configured by default. If it isn't configured what Zowe function will fail ? Is it the new installer, or something in a 1.3 existing build that will fall over ?

@OnnoVdT
Copy link
Contributor Author

OnnoVdT commented Jul 2, 2019

Looking at the name of the environment variable used to store the ssh port number (ZOWE_ZLUX_SSH_PORT), I would say something in zLUX will break if this is not set up, regardless of how it was installed.

@Joe-Winchester
Copy link
Member

ZLUX desktop contains two apps - a TN3270 terminal and a VT Terminal, which are effectively ways of logging into z/OS through a green screen or a terminal. By default these connect to 23 and 22 respectively, and the port can be overridden at install time so that the default ports are different if they have been changed on the host (e.g. to 2023 and 2022) which occurs on zD&T often for example. If openSSH isn't active and you can't open a termninal, the user failure is just that the VT terminal fails to open and displays a "can't connect screen". The other parts of Zowe - the 3270 - the explorers - the editors - the API gateway - will all continue to function.
This means that the pre-req isn't for Zowe per-say, it is for a particular app only. Because of that I don't think we should list it as a hard pre-req (in the same way that Java or node are for example), however we should add sections to the doc that cover each app and each pre-req in turn. With Cupids having the new launcher that does specific pre-req checking pre app I think is the place we should rewrite the docs, so for now I think the docs should stay as-is.

@nannanli
Copy link
Member

Closing this issue based on the discussion above. The system requirement doc will stay as is. Feel free to reopen if the problem or confusion persists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: docs Documentation issue or issues that have documentation impact area: misc This issue is a miscelleneous doc requirement not for a specific component or area
Projects
None yet
Development

No branches or pull requests

3 participants