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.

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:
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 continue.
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.
Select Add runbook.
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.

Select a runbook version.
Select Add runbook.
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 run in the order shown in 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 a new order to change the runbook sequence.

Select Next to continue.
3. Fleets
On the Fleets page, add fleets to a lifecycle operation schedule.
Select Add fleets.
In the Add fleets panel, perform the following steps:

Select the checkboxes next to the fleet names that require recurrent schedules.

Note

Only active fleets are displayed for selection.

To add the selected fleets, select Add fleets.

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 continue.
4. Runbook parameters
On the Runbook parameters page, enter one or more arguments for the runbook task, if any are defined.
- Patching or discovery runbook:
  
  Argument name: Select the argument name associated with the task.
  
  Argument value: Change the default value by entering a value.
  
  Apply same value wherever applicable in a runbook: To use the same value across runbook tasks, turn on this switch. If you don't turn on the switch, specify the argument name and value for each runbook task.
- Provisioning runbook:
  
  Based on the runbook and its tasks (for example, provisioning a database or Compute resource), Fleet Application Management displays relevant configuration fields. You can tailor configurations to the specific resource being provisioned.
  
  Note
  
  You can view and modify configurations associated with a Terraform package or configuration file (such as, JSON, YAML, or .tf files) during provisioning.
  
  Configurations are presented as dynamic forms, populated based on the contents of the underlying file (for example, key-value pairs).
  
  The form fields are generated from the schema.yaml file in the Terraform package. If a default value is defined in the schema, the field is pre-populated. Otherwise, the field appears blank for you to complete. For more information about schema.yaml file, see Meta Schema for Validation.
  
  To configure the runbook tasks, select one of these options:
  
  Select existing: Select an existing configuration catalog item. The runbook uses the selected configuration without changes. You can't modify the configuration in this step and no form is displayed.
  
  Create new: Select Change to create a catalog item by entering configuration values directly in the Create configuration catalog item panel. The panel displays a dynamic form rendered from the content of the schema.yaml file in the Terraform catalog item file attached to the runbook task. This new configuration can then be saved in Object Storage for future use. See Creating a Private Catalog Item. Fleet Application Management creates a catalog item and associates it with the provisioning task.
  Note
  
  Configuration fields adapt based on the resource type (such as, database, Compute, notifications, or events). For example, provisioning a notification service might prompt fields for email addresses, while a database provisioning runbook displays settings such as "Create Alarm Enabled" or "Create Event."
  Select Configure and select to confirm the configuration changes, create and select the configuration for the runbook.
Select Next to continue.
5. Review

On the Review page: To change settings, select Edit basic information.

Select Edit schedule to modify the schedule settings.

To modify runbooks, select Edit runbooks. For field descriptions, see Creating a Runbook.

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

To change input or output variables, select Edit parameters. 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.

Oracle Cloud Infrastructure Documentation

Creating a Lifecycle Operation Schedule

1. Basic information

Schedule

2. Runbook

3. Fleets

4. Runbook parameters

5. Review