Fixing a Fleet to Be Compliant
Configure runbook tasks and parameters for noncompliant fleets in Fleet Application Management.
On the Fleets list page, select the fleet that you want to work with. If you need help finding the Fleets list page or a specific fleet, see Listing Fleets.
On the details page for the fleet, select Fix now under the Compliance status section of the General information tab.
Fixing a fleet to be compliant consists of the following pages:
Run each of the following workflows in order. You can return to a previous page by selecting Previous.
1. Select runbooks
The Select runbooks page is where you add the required runbooks for the noncomplaint fleet.
After you add runbooks to the fleet, 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 position to change the runbook order.
2. 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.yamlfile 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 aboutschema.yamlfile, 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.yamlfile 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.
3. Review
On the Review page: To change settings, select Edit basic information.
To modify runbooks, select Edit runbooks. For field descriptions, see Creating a Runbook.
To change input or output variables, select Edit parameters. For field descriptions, see Creating a Task.
When the settings are fully verified, select Create.
A compliance fix job is created and you can find its progress from the Runbook processes tab. See Listing Runbook Processes. You can also find the compliance fix job by selecting the Jobs tab under Schedules.
Use the oci fleet-apps-management fleet-apps-management-operations scheduler-definition create command and required parameters to fix a noncompliant fleet:
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 fix a noncompliant fleet.