Skip to content

[enterprise-4.6] Remove refs to master in RT kernel #26513

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.

Sign up for GitHub

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

Merged
bobfuru merged 1 commit into from
Oct 15, 2020
Merged

[enterprise-4.6] Remove refs to master in RT kernel #26513

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 7 additions & 14 deletions modules/nodes-nodes-rtkernel-arguments.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,19 +13,17 @@ kernel includes a preemptive scheduler that provides the operating
system with real-time characteristics.

If your {product-title} workloads require these real-time characteristics,
you can switch your compute (worker) and/or master machines to the Linux
you can switch your machines to the Linux
real-time kernel. For {product-title}, {product-version} you can make this
switch using a MachineConfig object. Although making the change is as simple
as changing a MachineConfig `kernelType` setting to `realtime`, there are a few
other considerations before making the change:

[NOTE]
====
This procedure is fully supported with bare metal installations using
* Currently, real-time kernel is supported only on worker nodes, and only for radio access network (RAN) use.
* The following procedure is fully supported with bare metal installations that use
systems that are certified for Red Hat Enterprise Linux for Real Time 8.
Real time support in {product-title} is also limited to specific subscriptions.
This procedure is also supported for use with Google Cloud Platform
====
* Real-time support in {product-title} is limited to specific subscriptions.
* The following procedure is also supported for use with Google Cloud Platform.

.Prerequisites
* Have a running {product-title} cluster (version 4.4 or later).
Expand All @@ -35,7 +33,7 @@ This procedure is also supported for use with Google Cloud Platform

. Create a MachineConfig for the real-time kernel: Create a YAML file
(for example, `99-worker-realtime.yaml`) that contains a MachineConfig
object for the `realtime` kernelType. This example tells the cluster to
object for the `realtime` kernelType. This example tells the cluster to
use a real-time kernel for all worker nodes:
+
[source,terminal]
Expand All @@ -52,8 +50,6 @@ spec:
EOF
----
+
You can change `worker` to `master` to add kernel arguments to master nodes instead.
Create a separate YAML file to add to both master and worker nodes.

. Add the MachineConfig to the cluster. Type the following to add the MachineConfig
to the cluster:
Expand All @@ -65,7 +61,7 @@ $ oc create -f 99-worker-realtime.yaml

. Check the real-time kernel: Once each impacted node reboots, log in to the cluster
and run the following commands to make sure that the real-time kernel has
replaced the regular kernel for the set of worker or master nodes you
replaced the regular kernel for the set of nodes you
configured:
+
[source,terminal]
Expand All @@ -77,11 +73,8 @@ $ oc get nodes
[source,terminal]
----
NAME STATUS ROLES AGE VERSION
ip-10-0-139-200.us-east-2.compute.internal Ready master 111m v1.19.0
ip-10-0-143-147.us-east-2.compute.internal Ready worker 103m v1.19.0
ip-10-0-146-92.us-east-2.compute.internal Ready worker 101m v1.19.0
ip-10-0-156-255.us-east-2.compute.internal Ready master 111m v1.19.0
ip-10-0-164-74.us-east-2.compute.internal Ready master 111m v1.19.0
ip-10-0-169-2.us-east-2.compute.internal Ready worker 102m v1.19.0
----
+
Expand Down