-
Christoph Doerbeck
This guide is intended to support a series of workshop exercises for individuals getting familiar with Red Hat’s Openshift Container Platform version 4.
This is not an official Red Hat sponsored effort although I am currently employeed by Red Hat. Rather this is a tool I use to teach myself and those I interact with professionally about new and emerging technologies.
In the spirit of Opensource, I am attempting to make my work publicly accessible for reuse by others. Please be patient as I navigate my way through managing a day job while building out this project (workshop).
ℹ️
|
This whole effort is done using official Red Hat software and although things can be set up to work with upstream software components (CentOS, Origin, etc…) I currently do not have the bandwidth to support the development and testing of alternate build environments. |
💡
|
Extra info which could be helpful, but not essential for a given task or discussion |
ℹ️
|
Special information to pay attention |
|
Critical information which could help you avoid major set backs |
Each block of commands to execute will be labeled with the expected user-id and host. To enhance cut & paste efficiency, the command prompt is omitted from each line.
systemctl status sshd
Sample output will be titled with 'Your output should look like this' (or 'Command Output') and also be indented to help with visual identification. Sometimes there will also be footnotes and/or callouts.
● sshd.service - OpenSSH server daemon
Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2019-02-26 12:04:16 EST; 27min ago // (1)
Docs: man:sshd(8)
man:sshd_config(5)
Main PID: 3094 (sshd)
CGroup: /system.slice/sshd.service
└─3094 /usr/sbin/sshd -D
...<snip>...
-
This is the line we are interested in with a special note
The workshop often provides cheat-scripts to ease certain complex tasks. This helps the class stay focused and reduces the likelihood of errors and disruptions to the workshop delivery. Honestly, we are not here to learn vi
, emacs
or start debates about the merits of sed
and awk
.
The native commands which the cheat-scripts utilize will be documented in the following way.
cheat-service-status.sh
ℹ️
|
Native command(s) to verify system service systemctl status sshd |
There are three options to complete the lab.
-
Follow the instructions to download the ssh-key and use a local terminal for the majority of exercises
-
Skip downloading the ssh-key and simply use a local terminal with credentials provided by your instructors
-
The last bullet of the LAB INFORMATION page, provides a link 'to consoles'. By clicking that link, you can get true console access to "0WORKSTATION".
ℹ️
|
you will need true console (GUI) on "WORKSTATION" for the WebUI units. |
- asciidoctor-version
-
2.0.22
- safe-mode-name
-
secure