1. Log into Oracle Linux Automation Manager with an administrator user account.

2. From the Resources section, click Inventories.

   The Inventories page appears.

3. Click the Add button.

   A menu appears.

4. Click the Add Inventory option.

   The Create new inventory page appears.

5. In the Name field, enter a name for the inventory. For example, Inventory1.

6. In the Organization field, click the search button.

   The Select Organization dialog appears.

7. From the Organization list, select an organization.

8. Click Select.

9. In the Variables field (a code box), you can enter YAML or JSON code to specify any inventory variables by doing the following:

   1. Click the YAML or the JSON button to specify which syntax to use.
   2. Type the variables in the code edit box.

10. Click Save.

1. Click Groups.

   A list of Groups appears.

2. Click Add.

   The Create new group dialog appears.

3. In the Name field, add a name.
4. Click Save.

   The Group details page appears.

5. Click Related Groups.

   The Related Groups page appears.

6. Click Add.
7. Do one of the following:
   • To add an existing group, click Add existing group and choose one or more existing groups to relate to the existing group.
   • To add a new group, click Add new group and create a group that is related to the current group.
8. Click Save.

1. Log into Oracle Linux Automation Manager with an administrator user account.

2. From the Resources section, click Hosts.

   The Hosts page appears.

3. Click the Add button.

   The Create New Host page appears.

4. In the Name field, enter the IP address or host name.

5. In the Inventory field click the search button.

   The Select Inventory page appears.

6. From the inventory list, select an inventory.

7. Click Save.

   The Details page appears.

8. Set the host to On or Off to indicate whether the host is available for jobs or not.
9. Click Facts to review any facts gathered for the host from jobs run on the host. For more information about enabling fact storage, see Setting Up a Job Template.
10. Click Groups.

    A list of groups appears, if any are configured.

11. Click Add to add a group.
12. Select one or more groups from the list to add the host to the group. The groups that can be selected are created in the inventory that the host is associated with. For more information about creating groups, see Managing Inventories and Groups.
13. Click Save.

1. Log into Oracle Linux Automation Manager with an administrator user account.

2. From the Resources section, click Inventories.

   The Inventories page appears.

3. Click the Add button.

   A menu appears.

4. Click the Add Smart Inventory option.

   The Create new smart inventory page appears.

5. In the Name field, enter a name for the smart inventory.

6. In the Organization field, click search.

   The Select Organization dialog appears.

7. From the Organization list, select an organization.

8. Click Select.

   Note:

   You can only create smart inventories using inventories that are part of the same organization.
9. In the Smart host filter field, click the search icon.

   The Perform a search to define a host filter dialog appears.

10. To perform a search based on information configured in or generated by Oracle Linux Automation Manager, select one of the following:
    • Name: Enter either the full name of the host or a part of a name that might be shared by more than one host. For example, if you had several hosts where each name started with either eastern_region or western_region, you could select only those hosts in the eastern_region by entering eastern_region in this field.
    • Groups: Enter either the full group name or part of the group name. For example, if you have one host in group1 and another in group2, entering group displays both hosts. Entering group1 enters only hosts in group1. For more information about creating groups, see Managing Inventories and Groups.
    • Enabled: Set this to Yes to show all hosts available for jobs. Set it to No to display all hosts unavailable for jobs.
    • Inventory ID: Enter the inventory ID for an inventory. You can find the inventory ID for inventories using the api/v2/inventories/ REST API endpoint.
    • Instance ID: Enter the instance ID for a control or execution node instance. You can find the instance ID for inventories using the api/v2/instances/ REST API endpoint.
    • Last job: Enter the job ID of a job that ran against one or more hosts. Each host that the job ran against appears. To obtain the job ID, see Viewing Jobs.
    • Advanced: Perform more fine grained searches based on set types, various keys, and lookup types such as exact, startswith, and so on.
11. To perform an advanced search based on stored facts generated from running playbooks on existing hosts, do the following:
    1. Ensure a job has run to collect and store facts about the host to which this smart inventory applies. For more information about storing facts, see Setting Up a Job Template. For more information about viewing stored facts, see Managing Hosts.
    2. From the list, select Advanced.
    3. From the Key list, select ansible_facts.
    4. In the search field, enter the fact you want to search on. Valid parameters are:
       • () for groupings,
       • and for adding two groupings together,
       • __ to reference related fields in a relational field.
       • __ to indicate separate ansible_facts.
       • [] to indicate a JSON array in the path.
       For example, the following filters illustrate some of these parameters:
       • The following lists all Oracle Linux based hosts.

         ansible_distribution="OracleLinux"

       • The following lists all hosts within the IPv4 100.102.112.0 network. Within the host facts, this value is specified by two parameters: ansible_default_ipv4 and the nested parameter network. The use of the __ parameter in the search indicates that these are distinct but related parameters.

         ansible_default_ipv4__network="100.102.112.0"

       • The following lists all hosts using the AuthenticAMD processor. Within the host facts, this value is part of an array and appears within brackets [] after the ansible_processor parameter, and so brackets [] are used in the search for this kind of value.

         ansible_processor[]="AuthenticAMD"

12. After defining the search, click Select.

    The search appears within the Smart host filter field. Click the search icon again to add or remove searches.

13. In the Variables field (a code box), you can enter YAML or JSON code to specify any inventory variables by doing the following:

    1. Click the YAML or the JSON button to specify which syntax to use.
    2. Type the variables in the code edit box.

14. Click Save.

15. You can optionally configure Oracle Linux Automation Manager to update the memberships of smart inventories more frequently, by adding the following setting to the /etc/tower/conf.d/<configuration file>.py file (where <configuration file> is the name of the configuration file) on the control or hybrid nodes.

    AWX_REBUILD_SMART_MEMBERSHIP=True

    This updates memberships in the following events:

    • When a new host is added
    • When an existing host is modified (updated or deleted)
    • When a new Smart Inventory is added
    • When an existing Smart Inventory is modified (updated or deleted)

    Note:

    Enabling this parameter increases the load on the system.

• Manually by using the UI,
• Automatically according to a schedule,
• Automatically every time a job runs that uses the inventory.

1. Log into Oracle Linux Automation Manager with an administrator user account.

2. Create an inventory as described in Managing Inventories and Groups.
3. Create a project configured with access to a GIT inventory as described in Managing Projects.

4. From the Resources section, click Inventories.

   The Inventories page appears.

5. Select the inventory you created.
6. Click Sources.
7. Click Add.

   The Create new source page appears.

8. In the Name field, enter a name.
9. From the Execution Environment list, click the search button and select an execution environment to use when running the job that imports the inventory from the remote repository.

   Note:

   If you leave this field blank, the default execution environment is used. For more information about default execution environments, see Oracle Linux Automation Manager 2.3: Release Notes.

10. From the Source list, select Sourced from a Project.

    A new section appears called Source details.

11. From the Credential list, click the search button and select a credential to use, if required. For example, you could select a inventory file that requires further authentication, such as an inventory for Oracle Cloud Infrastructure (OCI) would require an OCI credential. For more information, see Setting Up an Oracle Cloud Infrastructure Credentials.
12. From the Project list, click the search button and select a project to use that includes a git repository which includes an inventory.
13. In the Inventory File field, enter the path and name of the inventory file. For more information about valid inventory formats, see Inventory File Formats.

    Note:

    The inventory path begins at the root directory of the git repository. If the inventory file is at the root level of the repository, enter the name of the repository file. If the inventory file is within one or more folders, enter the name of the first folder without a slash, then include slashes before each sub folder. For example, inventory/north_america/inventory.yaml.
14. As you type the path and name of the inventory file, the Set source to path to field appears and duplicates the inventory path and file name. When you have finished typing in the inventory path and file name, click this field to select the inventory.
15. From the Verbosity list, enter a verbosity level. This decides the level of output the inventory job update produces. Valid values are:
    • 0 (Warning)
    • 1 (Info)
    • 2 (Debug)
16. From the Update options area, select the following if required:
    • Overwrite: Enable this option to remove hosts and groups from the inventory that are no longer present in the external source. Unmanaged hosts and groups move to the next manual group or stay in the "all" group if none exist. If disabled, unmanaged hosts and groups remain unchanged during updates.
    • Overwrite variables: Enable this option to replace all variables for child groups and hosts with those from the external source. Disable it to merge local variables with external ones instead.
    • Update on launch: Enable this option so that whenever a job runs using this inventory, the inventory is refreshed first.
17. Click Save.
18. Click Sync to synchronize the source information. This triggers a synchronization job that you can view from the Jobs area. See Viewing Jobs for more information.
19. After the synchronization, return to the main inventory page and review the Hosts and Groups tab for imported host and group information.

• Sections start with a header in square brackets [], for example, [webservers].
• Each section represents a group or category of hosts.
• Section headers can't be empty.
• Modifiers can be added to section headers, such as:
  • :children to indicate that the group contains subgroups.
  • :vars to indicate that the group contains variables assigned to all members.

• Hosts are defined by listing their names under a section header, one per line.
• Hosts can have variables defined inline as key-value pairs separated by =.
• Ungrouped hosts must appear under the [ungrouped] section.

• Values passed in the INI format using the key=value syntax are interpreted differently depending on where they're declared within an inventory.
• When declared under a host, values are treated as host-specific variables.
• When declared under a group with the :vars modifier, values are treated as group-wide variables.
• When declared under the [ungrouped] section, values are treated as global variables.

[all.vars]
environment = "all"

[web.vars]
environment = "web"
timezone = "UTC"

[web.hosts.web1]
ansible_host = "192.0.2.254"
http_port = 80
server_name = "web1.example.com"
env_type = "production"
debug_mode = false

[web.hosts.web2]
ansible_host = "192.0.2.253"
http_port = 8080
server_name = "web2.example.com"
env_type = "production"
debug_mode = false

[web.hosts.dev-web1]
ansible_host = "192.0.2.252"
http_port = 8081
server_name = "dev-web1.example.com"
env_type = "development"
debug_mode = true

[web.hosts.dev-web2]
ansible_host = "192.0.2.251"
http_port = 8082
server_name = "dev-web2.example.com"
env_type = "development"
debug_mode = true

[db.vars]
database_version = "5.7"
backup_schedule = "daily"

[db.hosts.db1]
ansible_host = "192.0.2.250"
db_username = "admin"
db_password = "password"

{
    "hosts": [
        {
            "id": 1,
            "hostname": "host1.example.com",
            "ip_address": "192.168.1.101",
            "status": "active",
            "os": "Oracle_Linux_8",
            "location": "Ottawa",
            "owner": "User_4"
        },
        {
            "id": 2,
            "hostname": "host2.example.com",
            "ip_address": "192.168.1.102",
            "status": "inactive",
            "os": "Oracle_Linux_8",
            "location": "Texas",
            "owner": "User_1"
        },
        {
            "id": "3",
            "hostname": "host3.example.com",
            "ip_address": "192.168.1.10",
            "status": "active",
            "os": "Oracle_Linux_9",
            "location": "West_Coast",
            "owner": "admin_1"
        },
        {
            "id": "4",
            "hostname": "host4.example.com",
            "ip_address": "192.168.1.11",
            "status": "active",
            "os": "Oracle_Linux_9",
            "location": "West_Coast",
            "owner": "admin_2"
        },
        {
            "id": "5",
            "hostname": "host5.example.com",
            "ip_address": "192.168.1.15",
            "status": "inactive",
            "os": "Oracle_Linux_7",
            "location": "East_Coast",
            "owner": "user_1"
        },
        {
            "id": "6",
            "hostname": "host6.example.com",
            "ip_address": "192.168.1.16",
            "status": "inactive",
            "os": "Oracle_Linux_7",
            "location": "East_Coast",
            "owner": "user_2"
        },
        {
            "id": "7",
            "hostname": "host7.example.com",
            "ip_address": "192.168.1.16",
            "status": "inactive",
            "os": "Oracle_Linux_7",
            "location": "Ottawa",
            "owner": "user 3"
        }
    ]
}

1. Log into Oracle Linux Automation Manager with an administrator user account.

2. Display the left navigation menu if it's not already visible by switching the Global navigation menu button in the top-left corner of the page.

3. From the Resources section, click Credentials.

   The Credentials page appears.

4. Click the Add button.

   The Create New Credential page appears.

5. In the Name field, enter the name of the credential. For example, GitCredential1.

6. In the Organization field, click the search button.

   The Select Organization dialog appears.

7. From the organization list, select an organization.

8. Click Select.

9. From the Credential Type list, select Source Control.

10. In the UserName field, enter the username, if required.

11. In the Password field, enter a password, if required.

12. In the SCM Private Key field, enter the SSH private key (if you're using SSH authentication) that you set up on the host running Oracle Linux Automation Manager.

13. In the Private Key Passphrase field, enter a passphrase (if you have set up a passphrase for SSH authentication).

14. Click Save.

1. Log into Oracle Linux Automation Manager with an administrator user account.

2. Display the left navigation menu if it's not already visible by switching the Global navigation menu button in the top-left corner of the page.

3. From the Resources section, click Credentials.

   The Credentials page appears.

4. Click the Add button.

   The Create New Credential page appears.

5. In the Name field, enter the name of the credential. For example, OCICredential.

6. In the Organization field, click the search button.

   The Select Organization dialog appears.

7. From the organization list, select an organization.

8. Click Select.

9. From the Credential Type list, select Oracle Cloud Infrastructure.

10. In the User OCID field, enter the OCID.

11. In the Fingerprint field, enter a fingerprint.

12. In the Tenant OCID field, enter the tenant OCID.

13. In the Region field, enter the region.

14. In the Private Key field, enter the SSH private key.

15. In the Private User Key Passphrase field, enter a passphrase (if you have set up a passphrase for SSH authentication).

16. Click Save.

1. Log into Oracle Linux Automation Manager with an administrator user account.

2. Display the left navigation menu if it's not already visible by switching the Global navigation menu button in the top-left corner of the page.

3. From the Resources section, click Credentials.

   The Credentials page appears.

4. Click the Add button.

   The Create New Credential page appears.

5. In the Name field, enter the name of the credential. For example, InventoryMachineCredential1.

6. In the Organization field, click the search button.

   The Select Organization dialog appears.

7. From the organization list, select an organization.

8. Click Select.

9. From the Credential Type list, select Machine.

10. In the Username field, enter the username, if required.

11. In the Password field, enter a password, if required.

12. Select Prompt on launch checkbox above the Password field if you want a password prompt to appear when launching job templates or job workflows against an inventory.

13. In the SSH Private Key field, enter the SSH private key that Oracle Linux Automation Engine uses to access target hosts when using SSH authentication if required.

14. In the Signed SSH Certificate field, enter a signed SSH certificate, if required.

15. In the Private Key Passphrase field, enter a passphrase (if you have set up a passphrase for SSH authentication).

16. Select the Prompt on launch checkbox above the Private Key Passphrase field if you want a private key passphrase prompt to appear when launching job templates or job workflows against an inventory.

17. From the Privilege Escalation Method list, select an escalation method if the playbooks you run in the machine require an escalation method, for example, sudo.

18. In the Privilege Escalation Username field, enter the username, if required.

19. In the Privilege Escalation Password field, enter a password, if required.

20. Select Prompt on launch above the Privilege Escalation Password field if you want a password prompt to appear when launching job templates or job workflows against an inventory.

21. Click Save.

1. Log into Oracle Linux Automation Manager with an administrator user account.

2. Display the left navigation menu if it's not already visible by switching the Global navigation menu button in the top-left corner of the page.

3. From the Resources section, click Credentials.

   The Credentials page appears.

4. Click the Add button.

   The Create New Credential page appears.

5. In the Name field, enter the name of the credential. For example, Registry Credentials.

6. In the Organization field, click the search button.

   The Select Organization dialog appears.

7. From the organization list, select an organization.

8. Click Select.

9. From the Credential Type list, select Container Registry .

10. In the Authentication URL field, enter the IP address or host name of the container registry you want to connect with. For example, this might be a Private Automation Hub instance hosting your execution environment container images or it could be https://container-registry.oracle.com/. For more information about Private Automation Hub, see Oracle Linux Automation Manager 2.3: Private Automation Hub User's Guide.

11. In the Username field, enter the username of the container registry user that has access to the execution environment images you need.
12. In the Password or Token field, enter the password for the user.
13. Enable Verify SSL if the container registry is configured for SSL authentication.

14. Click Save.

1. Create a job template named RunSampleYumPlaybook that runs the playbook yum_update.yaml against an inventory of servers.

2. Create a job template named RunSampleApachePlaybook that runs the play book httpd.yaml against an inventory of servers.

3. Display the left navigation menu if it's not already visible by switching the Global navigation menu button in the top-left corner of the page.

4. From the Resources section, click Templates.

   The Templates page appears.

5. Click the Add button.

   A menu appears.

6. Click the Add workflow template option.

   The Create New Workflow Template page appears.

7. In the Name field, enter a name for the workflow template. For example, SampleWorkflowTemplate.

   Note:

   The Name field is the only mandatory field on this page. The organization and inventory fields, for example, don't have to be set at the workflow level.

8. Click Save.

   The Workflow Visualizer page is displayed in the browser with a Start button.

9. Click the Start button in the Workflow Visualizer page.

10. The Add Node dialog appears.

    1. The Node Type drop down list at the top of the Add Node dialog lets you select the type of resource to be added as a node. Accept the default choice of Job Template.

    2. Select RunSampleYumPlaybook from the list of available job templates.

    3. Accept the default option (Any) from the Convergence drop down list.

       Note:

       The property is only significant of the node you're adding has more than one parent converging on it.

    4. Optionally enter a Node Alias to the node to be displayed with a particular display name, different to the resource name, in the Workflow Visualizer.

    5. Click Save.

       The Add Node dialog is dismissed.

       The added node appears in the Workflow Visualizer.

11. Hover the mouse over the newly added node.

    A small toolbar appears within the Workflow Visualizer next to the node.

12. Click the add ("+") icon on the toolbar to add another node after the first node.

13. The Add Node dialog appears.

    1. As this is the second node in the sequence the dialog initially displays the following Run Type conditions to select from:
       • On Success.
       • On Failure.
       • Always.

       Accept the option selected by default (On Success).

    2. Click Next.

       The Add Node dialog at this stage displays the same fields (Node Type, Convergence, Node Alias) as discussed earlier in the instructions dealing with the first node.

    3. Select RunSampleApachePlaybook and complete the fields

    4. Click Save.

       The Add Node dialog is dismissed.

       The added node, RunSampleApachePlaybook, appears in the Workflow Visualizer.

       Note:

       The newly added node, RunSampleApachePlaybook, appears to the right of the first node (its parent) and the 2 nodes are connected by a green line (the green line indicates that the second node runs only after the first one completes successfully).

14. Click Save on the top-right of the Workflow Visualizer.

    The Workflow Visualizer is dismissed and the newly created workflow template is displayed with the details tab active.

15. Click Launch when you're ready to run the workflow.

    The Output page is displayed and the node currently in the running state is shown with a flashing green icon in its top left corner. The second node (RunSampleApachePlaybook) upon successful completion of the parent (RunSampleYumPlaybook).

    Upon successful completion of the workflow each job displays the time it took for it to complete

• OLAM EE

• Control Plane Execution Environment

1. Log into Oracle Linux Automation Manager.

2. Display the left navigation menu if it's not already visible by switching the Global navigation menu button in the top-left corner of the page.

3. From the Administration section, click Execution Environments.

   The Execution Environments page displays a summary table relating to the execution environments available in the system. The table columns include those described in the following list:

   • Name

     The Name column contains the name of the execution environment.

   • Image

     The Image column contains the full image location, including the container registry, image name, and version tag, of the image used for the execution environment. For example, container-registry.oracle.com/oracle_linux_automation_manager/olam-ee:latest . Alternatively, the image location might be a Private Automation Hub instance hosting the olam-ee image or a custom image. For more information see, Oracle Linux Automation Manager 2.3: Private Automation Hub User's Guide.

   • Organization

     The Organization column contains information about which organizations in your system can access the execution environment.

4. Click the name of an execution environment for more details.

   The execution environment is displayed in a tabbed view with the Details tab active. In addition to the Name, Image and Organization fields, the Details tab contains some other fields, including the following:

   • Created

     The Created field contains the date and time the execution environment was created.

   • Last Modified

     The Last Modified column contains the date and time the execution environment was last modified.

   • Pull

     The Pull field contains a value that stipulates the conditions under which Oracle Linux Automation Manager should pull the container image from its repository location before running a resource job. The following values are possible:

     • Always

       This option stipulates that a container image is always pulled before running the container.

     • Missing

       This option stipulates that a container image is only pulled if the image is not present before running the container.

     • Never

       This option stipulates that a container image never pulled before running the container.

       Important:

       Keep the container images updated to ensure the images have the latest CVE fixes.

5. Click the Back to execution environments button (the first button in the tab header row) to get back to the Execution Environments page.

1. Log into Oracle Linux Automation Manager.

2. Display the left navigation menu if it's not already visible by switching the Global navigation menu button in the top-left corner of the page.

3. From the Administration section, click Execution Environments.

4. Click Add.

   The Create new execution environment page appears.

5. In the Name field, enter the name of the execution environment.

6. In the Image field, enter the image location, including the container registry, image name, and version tag, of the image used for the execution environment. For example, container-registry.oracle.com/oracle_linux_automation_manager/olam-ee:latest . Alternatively, you can point to a Private Automation Hub instance hosting the olam-ee image or a custom image. For more information see, Oracle Linux Automation Manager 2.3: Private Automation Hub User's Guide.

7. From the Pull list, select one of the following values that stipulates the conditions under which Oracle Linux Automation Manager should pull the container image from its repository location before running a resource job:

   • Always

     This option stipulates that a container image is always pulled before running the container.

   • Missing

     This option stipulates that a container image is only pulled if the image isn't present before running the container.

   • Never

     This option stipulates that a container image never pulled before running the container.

     Important:

     Keep the container images updated to ensure the images have the latest CVE fixes.

8. Organization

   The Organization field contains information about which organizations in the system can access the execution environment.

9. Registry credential

   The Registry credential field contains information about which credential the system must use to connect to a container registry. For more information, see Setting Up Container Registry Credentials for an Execution Environment.

10. Click Save.

• One Job Queue per Instance Group

  Each instance group has its own job queue, and any node in the instance can process a job from that queue.

• Configuration of Extra Nodes

  The nodes initially available for association with Instance Groups are those you configured for the mesh topology during the installation process. If you require extra nodes, for example for a new instance group you have created, then you need to follow the same process you used to create the initial nodes (see Oracle Linux Automation Manager 2.3: Installation Guide for more information on configuring nodes for a mesh topology).

• Nodes Can Belong to More Than One Instance Group

  For example, you can make some nodes available across the cluster, whilst reserving others for a specific instance group.

• Associating Instance Groups With Resources

  By default, jobs are run on nodes in the Execution instance group you created during the installation process (see Oracle Linux Automation Manager 2.3: Installation Guide).

  However, if required, you can specify instance groups by associating them with one of the following resources:

  • Job Template

  • Inventory

  • Organization

  When a job runs, Oracle Linux Automation Manager first checks the job template associated with the job to see which instance group the job should be assigned to. If no instance group is associated with the job template, Oracle Linux Automation Manager next checks the inventory resource linked to the job. If no instance group is associated with the inventory resource, the Organization resource is checked.

• Instance Groups Provided by Default

  Oracle Linux Automation Manager comes with the following instance groups:

  • controlplane:

    The controlplane instance group contains control nodes. Control nodes run persistent Oracle Linux Automation Manager services, such as the task dispatcher, project and inventory updates, and system jobs, but not regular jobs. Control nodes don't have execution capability.

  • execution:

    The execution instance group contains execution nodes. Execution nodes run jobs under ansible-runner with podman isolation. Execution nodes only run user-space jobs.

1. Log into Oracle Linux Automation Manager with an administrator user account.

2. Display the left navigation menu if it's not already visible by switching the Global navigation menu button in the top-left corner of the page.

3. From the Administration section, click Instance Groups.

   The Instance Groups page appears.

• Name

  The Name column contains the name of the Instance Group. Clicking the name takes you to a tabbed view of that instance's properties. The Details tab is the active tab initially.

• Running Jobs

  The Running Jobs column contains the number of jobs associated with the instance group that are running.

• Total Jobs

  The Total Jobs column contains the sum of the number of jobs associated with the instance group that have completed, and the number of jobs associated with the group that are still running.

• Capacity

  The Capacity column displays a Used capacity progress bar that indicates the percentage of capacity of the instance group that's being used.

• Action

  The Action column displays an Edit instance group icon that lets you edit the instance.

1. Log into Oracle Linux Automation Manager with an administrator user account and navigate to the Instance Groups page.

2. In the summary table displayed on the Instance Groups page, go to the row with the group whose policy instance properties you want to edit.

3. Click the Edit instance group icon in the Action column.

   The Edit details page appears.

4. Enter values in the properties Policy instance minimum and Policy instance percentage fields.

5. Click Save.

   The tabbed view of the instance appears.

1. Log into Oracle Linux Automation Manager with an administrator user account and navigate to the Instance Groups page.

2. Click the Add button.

   A menu appears.

3. Click the Add instance group option.

   The Create new instance group appears.

4. In the Name field, enter a name for the instance group. For example, NodesForDataCentre1.

5. Optionally, enter integers into the Policy instance minimum and Policy instance percentage field.

   Note:

   The policy instance fields are defined as follows:

   • Policy instance minimum:

     This is the minimum number of instances to be automatically assigned to the group when new provisioned instances come online.

   • Policy instance percentage:

     Minimum percentage of all instances to be automatically assigned to this group when new provisioned instances come online

6. Click Save.

   The newly created instance group is displayed in a tabbed view with the Details tab active.

7. Click the Instances tab to switch to the Instances tab.

   The node instances associated with the group are displayed in a table.

8. To associate more node instances with the group, click the Associate button.

   The Select Instances dialog appears displaying available node instances.

9. Select the check boxes next to the nodes you want to associate with the group instance.

   Click Save.

   The Instances page is displayed and the nodes you selected appear in the list on the page.