1. Proposed title of this feature request

Support for hub cluster to be connnected on baremeatl and bmcs networks

2. What is the nature and description of the request?

When we deploy using agent-based a SNO that will be used as ACM/ZTP Hub cluster and when that node has two interface one for the bmc (e.g. 192.168.100.100) network and one for the rest (default route 10.10.10.225), the iconic cache asks the bmc to pull the image (virtual media) from the 10.10.10.225 that is not accessible

The error from the BMC

Request failed with FishyError: Failed fetching image from URL https://10.10.20.225:6183/redfish/boot-2c0a33b3-d22a-41ad-b420-7b21ff743f6e.iso: HTTPSConnectionPool(host='10.10.20.225', port=6183): Max retries exceeded with url: /redfish/boot-2c0a33b3-d22a-41ad-b420-7b21ff743f6e.iso (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f9c840dec70>: Failed to establish a new connection: [Errno 110] Connection timed out'))

3. Why does the customer need this? (List the business requirements here)

In Telco deployments based on baremetal, the BMCs network is isolated, without any access even via routing. Hence the partner want to allow the HUB cluster to have two ports, one connected to the baremetal network, in order to have access to the control plane of the cluster, and other port connected to the BMCs network, in order to interact with the BMCs of the servers that will be deployed as a spoke cluster. This BMCs network isolation is for security reasons.

4. List any affected packages or components.

ACM,Assisted Installer, ZTP