This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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.
The overall concept is not clear to me. For system firmware, I can download the firmware via the internet to the local HMC repository once and use it for further system updates of other systems. This way, I always have the latest firmware available. With I/O, I don’t have this option. Locally, I can only work with an "old" ISO file (-6 months). I can download I/O code via the internet but cannot reuse it locally in the HMC repository. I have to download it from the internet again and again for the same adapter type/level. This is a weak approach.
My approache is closer to:
-Centralized I/O Code Repository: A centralized repository for I/O code, similar to the HMC repository for system firmware, could be set up. This repository could be updated regularly from web so that the latest version is always available. This would allow you to download the code once and then use it for multiple systems.
-Automated Updates: Introduction of an automated update system that regularly downloads the latest I/O code versions from the internet and integrates them into the local repository. This way, you don't have to manually handle the downloading.
-Versioning and Management: Implementation of a versioning system that allows you to manage different versions of the I/O code and revert to older versions if needed. This could be integrated into a central management tool.
CHers Patrick