IBM System Storage Ideas Portal


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).


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

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. 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.

Add a new idea Subscribe
Status Not under consideration
Workspace Storage Scale (formerly known as GPFS)
Created by Guest
Created on Mar 21, 2022

RELATED IDEAS

Enhance policy handling to allow ordering of rules

I want to delete dirs and files in a subtree depending on their mtime. Using a policy file I can identify the files and dirs and order them by DIRECTORY_HASH to ensure the correct deletion order from deepest to highest paths. This works falwlessly when limited to run on ONE node only.

However, I CANNOT distribute this policy to run on multiple nodes in parallel as it can happen that node2 wants to delete a directory that still has content because node1 is still deleting data there but not yet finished.

In other words: the list is generated in the correct order but cut at arbitrary positions and distributed to the nodes.

The data needs to be processed in one policy as any file deletion will alter the mtime of the containing directory so deleting files first and then run another policy to delete the dirs will fail.

What is missing is some kind of dependency definition inside the policy. I'd like to tell the policy engine: "first process rule 1 and when you are completely done you may process rule 2".

An alternative to this would be a mechanism that let's the user influence where to cut the list before distributing to the nodes.

I think there are probably many similar problems that cannot be solved with the current implementation because of this restriction.

Idea priority Medium
  • Guest
    Reply
    |     Apr 13, 2022

    Thank you for submitting this Idea for Spectrum Scale. We will review this request and see if it is something we can implement in the near future.


    Sincerely,

    Spectrum Scale team

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.