You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a followup to #655. From Surbhi's research:
Does it support Ironic?
Ironic is supported, the docs just need lots of work and that is underway right now.
Bare metal provisioning uses Metal3, which leverages Ironic on the backend. However, this is currently for static networking only, without any ML2 plugin integration.
ML2 plugin integration is being focused only for BMaaS workloads.
It mean bare metal provisioning through Metal3 uses static networking without ML2 plugin integration. This means that network configurations must be pre-defined and cannot be dynamically adjusted by Neutron during provisioning.
BMaaS workloads that require dynamic networking will not function without ML2 plugin support.
The text was updated successfully, but these errors were encountered:
tzumainn
changed the title
Determine requirements for migrating MOC ESI to latest RedHat OpenStack
Determine requirements for migrating MOC ESI to latest Red Hat OpenStack
Dec 2, 2024
tzumainn
changed the title
Determine requirements for migrating MOC ESI to latest Red Hat OpenStack
Install Ironic on the new RH OpenStack deployment
Dec 7, 2024
This is a followup to #655. From Surbhi's research:
Ironic is supported, the docs just need lots of work and that is underway right now.
Bare metal provisioning uses Metal3, which leverages Ironic on the backend. However, this is currently for static networking only, without any ML2 plugin integration.
ML2 plugin integration is being focused only for BMaaS workloads.
It mean bare metal provisioning through Metal3 uses static networking without ML2 plugin integration. This means that network configurations must be pre-defined and cannot be dynamically adjusted by Neutron during provisioning.
BMaaS workloads that require dynamic networking will not function without ML2 plugin support.
The text was updated successfully, but these errors were encountered: