IBM Power Ideas Portal
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).
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.
With a stretched cluster this is available. Assign a site to the mirror pools via smitty hacmp and change lvm prederred read to siteaffinity. Scheduling policy has to be parallel write / sequential read for each lv in the vg.
It took you 5 years to find this out? I'm impressed.
This RFE didn't say anything about not changing LVM to achieve the required functionality. Very sad. You're giving away a big possible performance gain.
We save preferred copy value in LVM metadata to be persistent across varyoff/varyon. LVM (metdata) doesn't have any knowledge of which nodes the VG is varied on. Design limitation.
It is good idea if we can setup preferred read per node. We save preferred copy value in LVM metadata to be persistent across varyoff/varyon. LVM (metdata) doesn't have any knowledge of which nodes the VG is varied on. From LVM design it is not possible to provide preferred read per node.
It's 2020. How is it going?
This is not going to be available in 2016 or 2017 fall plan. The earliest we can consider this is in 2018 fall plan, it is too early to decide.
Creating a new RFE based on Community RFE #79352 in product IBM AIX.
I wanted to set this RFE public... the option was not selectable.
Feel free to change the RFE to public, it might get a few votes more in this case :-)