Clients Update Using Recurring Actions

This workflow shows how to automate updating the clients registered at SUSE Manager using recurring actions.

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 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.

Procedure 1: Creating a Recurring Action to Update Salt Itself

  1. 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 Home  My Organization  Recurring Actions and click Create.

  2. Select Action Type Custom State and enter a Schedule Name like update-salt.

  3. Select a schedule. For example, Weekly: Wednesday, 9:00 am .

  4. Assign the update-salt state by selecting the checkbox.

  5. Click Save Changes to save the action.

  6. You can edit the execution order of the states if needed. Click Confirm to confirm the order.

  7. Click Create Schedule to save the action.

Procedure 2: Creating a Recurring Action to Apply All Available Updates to the Systems

  1. 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 Systems  System Groups and click on infra-services.

  2. Now go to Recurring Actions and click Create.

  3. Select Action Type Custom State and enter a Schedule Name like full-system-update.

  4. Select a Schedule. For example, Weekly: Wednesday, 9:30 am . Keep enough time between this action and the update-salt action. The update-salt actions must be finished on all systems before this action should be executed.

  5. Assign the states util.syncall, certs, channels and uptodate by selecting the checkboxes. To perform a reboot afterwards you can also add reboot or rebootifneeded.

  6. Save the action by clicking Save Changes.

  7. You can edit the execution order of the states. The order should be util.syncall, certs, channels, uptodate and finally reboot or rebootifneeded if chosen. Click Confirm to store the order.

  8. Click Create Schedule to save the action.

Procedure 4: Creating a Recurring Action to Run a Highstate After the Update

  1. 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 Systems  System Groups and click infra-services.

  2. Go to Recurring Actions and click Create.

  3. Select Action Type Highstate and enter a Schedule Name like highstate.

  4. Select a Schedule. For example, Weekly: Wednesday, 10:30 am . Again, keep enough time between this action and the full-system-update action.

  5. Click Create Schedule to save the action.

5. Related Topics