Clients Update Using Recurring Actions
This workflow shows how to automate updating the clients registered at SUSE Manager using recurring actions.
The workflow is applicable for Salt clients only.
1. Use Case / Situation
Automated update of clients is benefitial when:
-
update of a large number of clients is wanted
-
the workflow should not be re-done every execution
-
a dedicated maintenance window exists.
2. Outcome / Resolution
Successful completion of this workflow results in consistent and supportable state.
3. Preparation
Before you start, you should have a number of Salt clients onboarded. It may make sense to have them sorted into groups you want to update together. In this workflow we use a system group named infra-services
.
4. Step-by-Step Workflow Instructions
To update a client two steps are required. A third step is optional but highly recommended to finalize the update process.
-
As an example, we create the action to update Salt itself as a recurring action for all systems in the organization. In the SUSE Manager Web UI, navigate to
and click Create. -
Select
Action Type
Custom State and enter aSchedule Name
likeupdate-salt
. -
Select a schedule. For example, Weekly: Wednesday, 9:00 am .
-
Assign the
update-salt
state by selecting the checkbox. -
Click Save Changes to save the action.
-
You can edit the execution order of the states if needed. Click Confirm to confirm the order.
-
Click Create Schedule to save the action.
-
As an example we create the action to apply all updates as a recurring action for a system group called "infra-services". In the SUSE Manager Web UI go to
and click oninfra-services
. -
Now go to
Recurring Actions
and click Create. -
Select
Action Type
Custom State and enter aSchedule Name
likefull-system-update
. -
Select a Schedule. For example, Weekly: Wednesday, 9:30 am . Keep enough time between this action and the
update-salt
action. Theupdate-salt
actions must be finished on all systems before this action should be executed. -
Assign the states
util.syncall
,certs
,channels
and`uptodate
by selecting the checkboxes. -
Save the action by clicking Save Changes.
-
You can edit the execution order of the states. The order should be
util.syncall
,certs
,channels
, and finallyuptodate
. Click Confirm to store the order. -
Click Create Schedule to save the action.
The |
uptodate
State is Applied-
In the SUSE Manager [web ui} go to
and click Create Key. -
Enter "mgr_reboot_if_needed" as
Key Label
and set asDescription
. Define if theuptodate
state should perform a reboot if needed. Set toFalse
if this is not wanted. -
Click Create Key to store the new key.
-
To assign values to multiple systems, navigate in the SUSE Manager Web UI to
and select the checkbox for all systems you want to modify. These system are not in the System Set Manager (SSM). -
Select in the left menu System Set Manager and select
in the tab bar. -
Click
mgr_reboot_if_needed
and enter False asValue
. -
Click Set Values to save.
-
As an example, we create the action to apply the highstate for the same group which was fully updated before. In the SUSE Manager Web UI, navigate to
and clickinfra-services
. -
Go to
Recurring Actions
and click Create. -
Select
Action Type
Highstate and enter aSchedule Name
likehighstate
. -
Select a Schedule. For example, Weekly: Wednesday, 10:30 am . Again, keep enough time between this action and the
full-system-update
action. -
Click Create Schedule to save the action.
5. Related Topics
-
For more information about recurring actions, see Recurring Actions.
-
For more information about custom info values, see カスタムシステム情報.