Description:

Oracle Cloud Infrastructure (OCI) imposes a limitation where the MAC addresses of instances cannot be determined in advance. This limitation prevents the assignment of host roles via the `agent-config.yaml` file during deployment. 

Ref: https://docs.openshift.com/container-platform/4.17/installing/installing_with_agent_based_installer/preparing-to-install-with-agent-based-installer.html#agent-host-roles_preparing-to-install-with-agent-based-installer 

OCI instances, however, support specifying a cloud-init script. This capability can be leveraged to dynamically assign a role to each instance.

Ref: https://docs.oracle.com/en-us/iaas/Content/ContEng/Tasks/contengusingcustomcloudinitscripts.htm 

The role assignment can then be processed by a new `systemd` service that runs conditionally on OCI instances.

Objectives:

1. Investigate the use of OCI's cloud-init script to embed role information into the instance configuration.
2. Explore the feasibility of a systemd service that:

• Detects whether it is running on an OCI instance.
• Reads the role assigned via cloud-init.
• Propagates this role to the agent configuration or a relevant service.

3. Evaluate potential edge cases, such as:

• Multiple roles per instance.
• Non-OCI environments misinterpreting OCI-specific configurations.

4. Instead of OCI's cloud-init script and the above steps, modify the agent installer client logic to first check if host mac address is provided, if not , fallback on hostname to assign a role.https://github.com/openshift/assisted-service/blob/f9683ac5e7680d74eb58fc3f35aa0b10b5774e69/cmd/agentbasedinstaller/host_config.go#L303 

This spike will help establish a robust mechanism to assign host roles in OCI environments without relying on MAC address information.