References to traditional clients removed (cont.) (#2786)

* Removed reference to traditional clients from reference/systems/system-details/sd-packages.adoc * Removed reference to traditional clients from modules/client-configuration/pages/system-set-manager.adoc * Removed reference to traditional clients from modules/client-configuration/pages/virt-xenkvm.adoc * Removed reference to traditional clients from modules/administration/pages/actions.adoc * Update modules/administration/pages/actions.adoc Co-authored-by: Karl Eichwalder <ke@suse.de> --------- Co-authored-by: Karl Eichwalder <ke@suse.de>
uyuni-project · Feb 13, 2024 · 06568a2 · 06568a2
1 parent 945e5fe
commit 06568a2
Show file tree

Hide file tree

Showing 4 changed files with 38 additions and 108 deletions.
diff --git a/modules/administration/pages/actions.adoc b/modules/administration/pages/actions.adoc
@@ -57,12 +57,6 @@ Navigate to menu:Home[My Organization > Recurring Actions] to see all recurring
 {productname} Administrators can set and edit recurring actions for all clients in all organizations.
 Navigate to menu:Admin[Organizations], select the organization to manage, and navigate to the menu:States[Recurring Actions] tab.
 
-[NOTE]
-====
-Recurring actions can only be used with Salt clients.
-Traditional clients in your group or organization are ignored.
-====
-
 
 
 == Action Chains
@@ -144,70 +138,29 @@ For more information about subscribing to software channels, see xref:client-con
 
 [IMPORTANT]
 ====
-For transactional update systems, consider that a remote command is run inside a single snapshot.
-This can cause some limitations.
+//* For transactional update systems, consider that a remote command is run inside a single snapshot.
+//  This can cause some limitations.
 
 ifeval::[{uyuni-content} == true]
-For more information, see xref:client-configuration:clients-slemicro.adoc[] and xref:client-configuration:clients-opensuseleapmicro.adoc[].
+* For transactional update systems, consider that a remote command is run inside a single snapshot.
+  This can cause some limitations.
+  For more information, see xref:client-configuration:clients-slemicro.adoc[] and xref:client-configuration:clients-opensuseleapmicro.adoc[].
 endif::[]
 
 ifeval::[{suma-content} == true]
-For more information, see xref:client-configuration:clients-slemicro.adoc[].
+* For transactional update systems, consider that a remote command is run inside a single snapshot.
+  This can cause some limitations.
+  For more information, see xref:client-configuration:clients-slemicro.adoc[].
 endif::[]
-====
 
+* Remote commands are run from the [path]``/tmp/`` directory on the client.
+  To ensure that remote commands work accurately, do not mount ``/tmp`` with the [parameter]``noexec`` option. 
+  For more information, see xref:administration:troubleshooting/tshoot-mounting-tmp-with-noexec.adoc[Troubleshooting Mounting /tmp with noexec].
 
-
-.Procedure: Configuring Traditional Clients to Accept Remote Commands
-. On the client, at the command prompt, use the package manager to install the [systemitem]``rhncfg``, [systemitem]``rhncfg-client``, and [systemitem]``rhncfg-actions`` packages, if not already installed.
-    For example:
-+
-----
-zypper in rhncfg rhncfg-client rhncfg-actions
-----
-. On the client, at the command prompt, as root, create a path in the local configuration directory:
-+
-----
-mkdir -p /etc/sysconfig/rhn/allowed-actions/script
-----
-+
-. Create an empty file called [path]``run`` in the new directory.
-    This file grants the {productname} Server permission to run remote commands:
-+
-----
-touch /etc/sysconfig/rhn/allowed-actions/script/run
-----
-
-[IMPORTANT]
-====
-For Salt clients, remote commands are run from the [path]``/tmp/`` directory on the client.
-To ensure that remote commands work accurately, do not mount ``/tmp`` with the [parameter]``noexec`` option.
-For more information, see xref:administration:troubleshooting/tshoot-mounting-tmp-with-noexec.adoc[Troubleshooting Mounting /tmp with noexec].
-====
-
-[WARNING]
+* All commands run from the [guimenu]``Remote Commands`` page are executed as {rootuser} on clients.
+  Wildcards can be used to run commands across any number of systems.
+  Always take extra care to check your commands before issuing them.
 ====
-All commands run from the [guimenu]``Remote Commands`` page are executed as {rootuser} on clients.
-Wildcards can be used to run commands across any number of systems.
-Always take extra care to check your commands before issuing them.
-====
-
-
-
-.Procedure: Running Remote Commands on Traditional Clients
-. In the {productname} {webui}, navigate to [guimenu]``Systems``, click the client to run a remote command on, and navigate to the menu:Details[Remote Command] tab.
-. In the [guimenu]``Run as user`` field, type the user ID (UID) of the user on the client that you want to run the command.
-    Alternatively, you can specify a group to run the command, using the group ID (GID) in the [guimenu]``Run as group`` field.
-. OPTIONAL: In the [guimenu]``Timeout`` field, type a timeout period for the command, in seconds.
-    If the command is not executed within this period, it is not run.
-. In the [guimenu]``Command label`` field, type a name for your command.
-. In the [guimenu]``Script`` field, type the command or script to execute.
-. Select a date and time to execute the command, or add the remote command to an action chain.
-. Click btn:[Schedule] to schedule the remote command.
-
-For more information about action chains, see xref:reference:schedule/action-chains.adoc[].
-
-
 
 
 .Procedure: Running Remote Commands on Salt Clients

diff --git a/modules/client-configuration/pages/system-set-manager.adoc b/modules/client-configuration/pages/system-set-manager.adoc
@@ -15,33 +15,32 @@ The icons in this table indicate:
 * {question} this action is under consideration for this client type, and may or may not be supported at a later date.
 
 .Available SSM Actions
-[cols="1,1,1", options="header"]
+[cols="1,1", options="header"]
 |===
 
-| Action                    | Traditional   | Salt
-| List systems              | {check}       | {check}
-| Install patches           | {check}       | {check}
-| Schedule patch updates    | {check}       | {check}
-| Upgrade packages          | {check}       | {check}
-| Install packages          | {check}       | {check}
-| Remove packages           | {check}       | {check}
-| Verify packages           | {check}       | {cross}
-| Create groups             | {check}       | {check}
-| Manage groups             | {check}       | {check}
-| Channel memberships       | {check}       | {check}
-| Channel subscriptions     | {check}       | {cross}
-| Deploy/diff channels      | {check}       | {cross}
-| Autoinstall clients       | {check}       | {cross}
-| Tag for snapshot          | {check}       | {cross}
-| Remote commands           | {check}       | {cross}
-| Power management          | {check}       | {cross}
-| Update system preferences | {check}       | {check}
-| Update hardware profiles  | {check}       | {check}
-| Update package profiles   | {check}       | {check}
-| Set/remove custom values  | {check}       | {check}
-| Reboot clients            | {check}       | {check}
-| Migrate clients to another organization | {check} | {check}
-| Delete clients            | {check} | {check}
+| List systems              | {check}
+| Install patches           | {check}
+| Schedule patch updates    | {check}
+| Upgrade packages          | {check}
+| Install packages          | {check}
+| Remove packages           | {check}
+| Verify packages           | {cross}
+| Create groups             | {check}
+| Manage groups             | {check}
+| Channel memberships       | {check}
+| Channel subscriptions     | {cross}
+| Deploy/diff channels      | {cross}
+| Autoinstall clients       | {cross}
+| Tag for snapshot          | {cross}
+| Remote commands           | {cross}
+| Power management          | {cross}
+| Update system preferences | {check}
+| Update hardware profiles  | {check}
+| Update package profiles   | {check}
+| Set/remove custom values  | {check}
+| Reboot clients            | {check}
+| Migrate clients to another organization | {check}
+| Delete clients            | {check}
 |===
 
 

diff --git a/modules/client-configuration/pages/virt-xenkvm.adoc b/modules/client-configuration/pages/virt-xenkvm.adoc
@@ -78,14 +78,6 @@ For more information about creating a bootstrap script, see xref:client-configur
 
 
 
-////
-// Still any limitations for Salt clients?
-[IMPORTANT]
-====
-Autoinstallation of VM guests works only if they are configured as Traditional clients.
-Salt clients can be created using a template disk image, but not by using {ay} or {kickstart}.
-====
-////
 
 
 

diff --git a/modules/reference/pages/systems/system-details/sd-packages.adoc b/modules/reference/pages/systems/system-details/sd-packages.adoc
@@ -24,20 +24,6 @@ Click the name of a package to see more information.
 To install packages, check the package in the list and click btn:[Install Selected Packages].
 Any EULAs will be accepted automatically.
 
-Verify::
-Traditional clients only.
-Lists packages available for verification against the package repository.
-Click the name of a package to see more information.
-To verify a package, check the package in the list and click btn:[Verify Selected Packages].
-When the verification is complete, navigate to menu:Systems[Events > History] to see the results.
-
-Lock::
-Traditional clients only.
-Lists packages that are locked on the selected client.
-To lock a package, check the package in the list and click btn:[Request Lock].
-To remove a package lock, check the package in the list and click btn:[Request Unlock].
-For more information about package locks, see xref:client-configuration:system-locking.adoc[].
-
 Profiles::
 Compare packages installed on the selected client with a stored profile, or with packages installed on another client.
 When the comparison is made, you can choose to modify the selected client to match.