bond support on bare metal IPI

[chz8494]

Version

$ openshift-install version
4.4

Platform:

baremetal

Please specify:

• IPI

What happened?

Actually need few answers for following questions:

1. I only see guide about enabling bond through kernel options on RHCOS UPI, is there a way to enable bond/port-channel on IPI? seems IPI yaml has option to define which interface to be used as for data, I'd expect that interface can be bond too, but the bond interface has to be pre-created by something, would it be included in bootstrap? I know Openstack ironic can do that, just don't see this part in Openshif IPI script.
2. There are other use cases too for customized network setup on bare metal, such as isolating mgmt/data/storage/sriov, I don't want to put them all in same interfaces, so far I can't find such example anywhere in your documents, bond support is only one of this use cases. Anyhow, I feel IPI is not officially fully supported, are you encouraging users to create their own automation process to install openshift in a UPI kind of way?
3. Is there a way to manage/PXE boot RHCOS hosts in a way like ubuntu MaaS for Redhat? That would make things much easier.

[hardys]

This is a known issue for IPI baremetal deployments, currently the only solution is to use either MachineConfig customization or ignition customizations ref https://github.com/openshift/installer/blob/master/docs/user/customization.md

That may be sufficient to configure the primary controlplane network on a bond, but it is not sufficient e.g if you also require a non-default VLAN.

Further discussion in:

coreos/ignition#979

openshift/machine-config-operator#1690

openshift/enhancements#394

/label platform/baremetal

openshift/enhancements#399

[chz8494]

@hardys I don't see how machineconfig works with bond on that page.
For ignition config, is there a full example? I see the simple example at the end of that document talking about increasing http timeout. I would assume to put any extra config in worker.ign or master.ign? where are these files in installer? are they auto generated? so to enable bond it'd be like putting this in worker.ign?

  "networkd": {
    "units": [
      {
        "name": "00-eth.network",
        "contents": "[Match]\nName=eth*\n\n[Network]\nBond=bond0"
      },
      {
        "name": "10-bond0.netdev",
        "contents": "[NetDev]\nName=bond0\nKind=bond"
      },
      {
        "name": "20-bond0.network",
        "contents": "[Match]\nName=bond0\n\n[Network]\nDHCP=true"
      }
    ]
  }

I feel this may work to initialize an openshift cluster, but what if we need to expand cluster like adding more nodes later? I don't see there's any option in Openshift metal node managment for creating new bond interface and use it on new node.

[chz8494]

plus I don't see bare metal option in create-config command. Anyhow, I feel this version of Openshift is not well organized and documented, and not user friendly to bare metal users at all. :(

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.