Integration
This is an IBM Automation portal for Integration 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).
Shape the future of IBM!
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:
Search existing ideas
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 your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
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.
I agree that we need to move CP4I in this direction, unfortunately there are (as John mentioned) some complexities with catalog mirroring. Mirroring a whole catalog can increase the amount of mirror data, which is something we've worked hard to reduce in our current toolchain and would need to work out how to do the same using
oc mirrorinstead.Consolidating on one process is definitely where we're going, but going to take time.
I think it is critical to have a uniform tool set and process for installing any Cloud Pak using air-gapped installation. There needs to be agreement between IBM and Red Hat and that agreement needs to work reliably for customers.
I have a joint customer that is having the same difficulty -- large IBM and RH shop thats nearly 100% offline. 2 different procedures and tools for one platform (OCP). I am not a huge fan of oc-mirror we ship due to nagging customer issues with the tool (especially around operators) but there should be a unified experience when it comes to caching standard content. We dont ask customers to use 2 different tools for RPMs on linux, so should it be for OCI.
CP4I should follow the Red Hat recommendation and build on it
This week, I had this same request from two different customers deploying OCP in an air-gapped environment and also consuming IBM CloudPaks. They asked basically the same question: why do we have two entirely different processes to accomplish the same goal ? (which is mirror container images to a private container registry) - wouldn't it be less confusing and more efficient to use the same tool to mirror OCP to also mirror the content from the IBM CloudPaks? After all we are just mirroring container images to a private container registry.
Great idea