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:
Post your ideas
Start by posting ideas and requests to this portal to enhance a Power product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas and add comments to ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The Power teams will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Specific link you will want to bookmark for future use
IBM Unified Ideas Portal-https://ideas.ibm.com/- Use this site to create or search for existing Ideas across all IBM products that are outside of Power, and track all of your personal interactions with all Ideas.
Update "verify" error message - Disk does not attached to FC Group
When a verify is run too soon after a discovery is run, the error "Disk does not attached to FC Group" is shown. Besides the grammatical correction needed, VMRMDR needs to have its error logic updated to reflect what is truly happening - VMRM call...
Display resource requirements/availability in the GUI
Local resources (requirements) should not exceed the remote resources (availability). As new VMs are added to local servers, sometimes the remote resources available can be exceeded. This would prevent a successful Move or Rehearsal. There is no "...
Possibility to 'quiesce' (or 'unmanage') entire VMRM cluster during SW upgrades
Under 'Description' write the details of your new idea: On a 'HA' cluster with 2 Hosts we had to upgrade the HMCs from v9 to v10, during the upgrade the KSYS logged the event HMC_UNREACHABLE even though it's expected that the HMC may not be Fully ...
ksysmgr - do not suggest running discover on empty workgroup
When the last VM is removed from a workgroup, ksysmgr should not suggest running a "discovery to apply changes" (should say "discover" as there is no "discovery" process) against the empty workgroup because it is not needed and the resulting retur...
Remove host from cluster when removed from host_group
The host should be completely removed from the cluster when it is removed from a host_group. This would match the same action occurring with VMs - they are completely removed from the cluster when they are removed from a workgroup.
Do not place IBM confidential, company confidential, or personal information into any field.