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.
Hello,
I believe the most appropriate approach would be to allow defining the Storage Pool according to the desired storage tier — for example: Standard, Premium, Glacier, Glacier Deep Archive, and so on.
Some of these tiers could be specifically configured with the retrieve option, similar to the S3 Glacier behavior, ensuring a transparent recall process for archived data.
We currently have demands exceeding 4 PB of data intended for Storage Archive, but without this functionality, system administration becomes significantly more complex.
Considering how IBM Storage Scale operates and its multi-tier data management model, implementing such functionality for S3 would be essential to optimize both operations and management of large-scale data in hybrid environments.
It would be very convenient if the following option were available, even though I understand it is not compatible with the S3 standard:
Files in the migrated state could automatically have the extended attribute { user.storage_class: "GLACIER" }.
Files in the premigrated or resident state could automatically have the extended attribute { user.storage_class: "STANDARD" }.
At this point, the put-bucket-lifecycle-configuration feature is not essential for my use case.