-
Feature Request
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
None
-
None
-
Product / Portfolio Work
-
None
-
False
-
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
-
None
1. Proposed title of this feature request
BareMetal as a Service (BMaaS) support for OpenShift Metal3
2. What is the nature and description of the request?
Customers are looking for ways to manage their fleet of BareMetal machines. The current Red Hat offering can solve this with OpenStack Ironic, however many customers perceive OpenStack as a Legacy technology and are moving towards OpenShift for their IaaS needs.
The OpenShift platform has already adapted Ironic in for of metal3 project. This request is to expand the use case from just deploying coreOS to other operating system such as RHEL or Windows
3. Why does the customer need this? (List the business requirements here)
- we are working with customers currently managing around 20k baremetal nodes with Ironic that considers OpenStack a legacy platform and is looking to migrate to OpenShift
- one platform to manage containers, VMs and BareMetal
- ability to rapidly provision and deprovision BareMetal instances with any Operating System - Linux, Windows
- ability to provision nodes over multiple networks
- ability to store bm os images
- use of multi-tenancy of the Baremetal - either with DPUs or other means to separate tenants - the customer is providing the Baremetal as a Service to their clients
4. List any affected packages or components.
- OpenShift
- Metal3
- nmstate
- metallb
- is caused by
-
OCPSTRAT-2405 [GA] BareMetal as a Service Support for OpenShift
-
- New
-
-
OCPSTRAT-1819 [Tech Preview] BareMetal as a Service Support for OpenShift
-
- Closed
-