Creating a Lifecycle Operation Schedule

Create a schedule to perform lifecycle operations daily or monthly in Fleet Application Management based on the release of patches.

• Console
• CLI
• API

• On the Schedules list page, select Create schedule. If you need help finding the list page, see Listing Lifecycle Operation Schedules.

  Creating a schedule consists of the following pages:

  • 1. Basic information

  • 2. Runbook
  • 3. Fleets
  • 4. Runbook parameters

  • 5. Review

  Run each of the following workflows in order. You can return to a previous page by selecting Previous.

  1. Basic information

  The Basic information page is where you provide the basic information for a lifecycle operation schedule in Fleet Application Management.

  Enter the following information:

  • Name: Enter a unique name for a lifecycle schedule. Avoid entering confidential information.
  • Description: Enter a description for the lifecycle schedule. Avoid entering confidential information.
  • Create in compartment: Select the compartment where the schedule should be created.

  Schedule

  Select a schedule type to configure schedule for a lifecycle operation.

  Select one of the following options:

  • Maintenance window: To select a schedule from the list of existing maintenance windows, select this option. Then, select a maintenance window from the maintenance window list table that you want to be part of the schedule. In the list table, select the name of a maintenance window to open its details page, where you can view its status and perform other tasks. If you need help finding the list page or the maintenance window, see Listing Maintenance Windows.
  • Custom: To enter a specific schedule for a fleet, select this option. For field descriptions, see Creating a Maintenance Window.

  Select Next to proceed to the next step.

  2. Runbook

  On the Runbooks page, select a runbook from a compartment associated with specific lifecycle operations and then select its suitable version.

  Note
  
  Ensure you have the correct permissions for the SUDO access when selecting a runbook with SUDO permissions enabled.

  1. Select Add runbook.
  2. In the Add runbook panel, select the runbook that you want to include in the schedule.
     Note
     
     Only active runbooks are displayed for selection.

     These runbooks can be applied when patches are installed.
  3. Select a runbook version.
  4. Select Add runbook.
  5. To add runbooks from another compartment, select that compartment and repeat the preceding steps.

  After you add runbooks to the schedule, they appear in the Add runbook table. The runbooks are executed based on the execution order displayed on the table. You can perform the following actions:

  • Select the runbook name to get more details.
  • From the Actions menu () in the row for that runbook, select an appropriate order to alter the execution order.

  Select Next to proceed to the next step.

  3. Fleets

  On the Fleets page, add fleets to a lifecycle operation schedule.

  1. Select Add fleets.
  2. In the Add fleets panel, perform the following steps:
     1. Select the checkboxes next to the fleet names that require recurrent schedules.
        Note
        
        Only active fleets are displayed for selection.
     2. To add the selected fleets, select Add fleets.
  3. To add fleets from another compartment, select that compartment and repeat the preceding steps.
     After you add fleets, you can verify whether conflicts are reported in the fleet schedule and take necessary action by selecting Check fleet schedule conflicts. For instructions, see step 4 in Verifying Fleet Schedule Conflicts using the Console.

  After you add fleets to the schedule, they appear in the Add fleets table. You can perform the following actions:

  • Select the fleet name to get more details.
  • Select the checkbox next to the fleet and select Remove to remove it from the schedule.

  Select Next to proceed to the next step.

  4. Runbook parameters

  The Runbook parameters page is where you enter one or more arguments for the runbook task if arguments were defined.

  • Argument name: Select the argument name associated with the runbook task if there were parameters associated with the runbook.
  • Argument value: To change the default argument value, enter an argument value.
  • Apply same value wherever applicable in a runbook: To apply the same argument value across runbook tasks, turn on this toggle. If you don't turn on the toggle, enter an argument name and value under Patch OS.

  Select Next to proceed to the next step.

  5. Review

  Review the contents of the Review page. Select Edit basic information to change settings.

  Select Edit schedule to modify the schedule settings.

  Select Edit runbooks to modify the runbook settings. For field descriptions, see Creating a Runbook.

  Select Edit fleets to modify the fleet settings. For field descriptions, see Creating a Fleet.

  Select Edit parameters to modify the input and output variables of a task. For field descriptions, see Creating a Task.

  When the schedule settings are fully verified, select Create to create a schedule and list it on the Schedules list page.

• Use the oci fleet-apps-management fleet-apps-management-operations scheduler-definition create command and required parameters to create a schedule:

  oci fleet-apps-management fleet-apps-management-operations scheduler-definition create --action-groups <json_file_or_string> --compartment-id <compartment_OCID> --schedule <json_file_or_string> [OPTIONS]

  For a complete list of flags and variable options for Fleet Application Management CLI commands, see the CLI for Fleet Application Management.

• Run the CreateSchedulerDefinition operation to create a schedule.