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 Not under consideration
Created by Guest
Created on Apr 12, 2018

Concurrent upgrades for Spectrum Scale Protocol Nodes

Currently, upgrades to Spectrum Scale are disruptive, documented to be 20 minutes per node. The stated reason is that SMB versions cannot co-exist, however, it is likely that not all upgrades introduce a new version of SMB.

Idea priority Urgent
  • Guest
    Reply
    |
    Sep 30, 2020

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - IBM Spectrum Scale
    Product - Spectrum Scale (formerly known as GPFS) - Private RFEs
    Component - Product functionality

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - IBM Spectrum Scale
    Product - Spectrum Scale (formerly known as GPFS) - Private RFEs
    Component - V4 Product functionality

  • Guest
    Reply
    |
    Apr 25, 2019

    Given the architecture of Samba and CTDB in particular, the current downtime of a few minutes is the best achievable. To completely eliminate the downtime would require either major development effort by the Samba project, or replacing Samba entirely for SMB/CIFS support

  • Guest
    Reply
    |
    Aug 30, 2018

    Sorry, yes, I thought I was responding to a different RFE.

    The issue here is definitely with the need to restart CIFS services. Your competitors in the NAS market do not require such outages when CIFS is updated. The required outage makes scheduling upgrades more difficult in a production environment.

  • Guest
    Reply
    |
    Aug 28, 2018

    It looks like the Information Provided may have been submitted against the wrong RFE? Here is the request for more information again:
    Scale already supports concurrent (rolling) upgrades. Individual nodes can be disrupted during a Scale upgrade, however the cluster itself and its services can continue running without interruption. There are a few exceptions to this. In particular, if SMB needs to be upgraded, it must be briefly shut down before restarting in the new version. However, this only affects SMB and does not interrupt any other services on the cluster. By following best practices, it only interrupts SMB itself for a brief period, as little as a few minutes, not 20 minutes per node. However, if SMB itself does not need to be upgraded, the Installer should detect this and should not interrupt SMB service. Does this address the request?

  • Guest
    Reply
    |
    Aug 24, 2018

    The issue here is specific to the management node. Currently, if the management node fails, it is necessary to either do without it, or to set up a warm standby. I am asking for the ability to have a secondary management node that automatically takes over as necessary.

    This is specific to ESS.

  • Guest
    Reply
    |
    Aug 23, 2018

    Scale already supports concurrent (rolling) upgrades. Individual nodes can be disrupted during a Scale upgrade, however the cluster itself and its services can continue running without interruption. There are a few exceptions to this. In particular, if SMB needs to be upgraded, it must be briefly shut down before restarting in the new version. However, this only affects SMB and does not interrupt any other services on the cluster. By following best practices, it only interrupts SMB itself for a brief period, not 20 minutes per node.

  • Guest
    Reply
    |
    May 30, 2018

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - IBM Spectrum Scale
    Product - Spectrum Scale (formerly known as GPFS) - Private RFEs
    Component - V4 Product functionality
    Operating system - Other
    Source - Storage Technical Client Council

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - Storage
    Product - Storage TCC - Private Requests
    Component - Other
    Operating system - Other
    Source - Storage Technical Client Council