This portal is to open public enhancement requests against IBM System Storage products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
we might(?) be able to build on the same MGEN bring up automation used by HCI today to boot an HCI box up to the point where it can provide an IPI compliant endpoint for the OpenShift installer, using freshly deployed OCPVirt instead of a traditional hypervisor control plane. I imagine there is an ACM swim lane in this to consider as well...
Sharing further on this - I believe that if the HCI platform included a control plane/API that could be consumed by the openshift installer in the same way other IPI providers are consumed, then we would have much greater addressable market and be in a much stronger competitive position.
In the idea above I call out how other IBM providers are already included in the RHT doc as supported targets for IPI and UPI installation. I do this to illustrate how achieving this functionality translates into core RHT documentation, similar to current doc today that does same for directly competing platforms - a rock solid endorsement that it's an architecture supported by RHT too, backed by the necessary joint engineering/QA.
Updated original idea to correct and clarify