Skip to Main Content
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.

Status Future consideration
Created by Guest
Created on Jun 12, 2023

using remote clients as helper nodes for policy scans and processing migration

Usually, IBM recommends to pool all ESS Storage Servers in a so called storage cluster and then  connect one or multiple remote client / or so called / compute clusters to the ESS. In fact, thats meanwhile a common best practice cluster topology. 
On the other hand , for performance reasons and to keep the storage cluster as robust as possible, any addtional wokrload - other than doing NSD work - should not be scheduled to the ESS NSD servers. 

So a customer , having the need to work with policies, is in trouble, because policy action needs to be run in the cluster, that "owns" the file system, which is by nature the ESS cluster. 

in adition: 

A reasonable performance impact, when using policy engine , is the number of involved nodes. typically, customers have hundreds or thousands of nodes... but in the compute cluster. The number of nodes in the storage cluster a failry small..

 

Therfore we would like to see  the enhancement, that we can use the remote client nodes to do policy work. 

There is an already existing EPIC  291831  to that, but this Epic only adress's half of the issue - the scanning phase. Here, by this IDEA, we want to also get the processing/migration part included. 

 

Idea priority High