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.

ADD A NEW IDEA

All ideas

Showing 68

Provide qualified third-party firmware upgrade software packages with ClevOS

ClevOS currently provides IBM branded hardware firmware upgrade packages as part of the ClevOS appliance image. It has been requested to also include similar upgrade packages for COS qualified third-party appliances, such as the HP devices and the...
about 2 years ago in Cloud Object Storage System 0 Submitted

Virgina Tech: Allow/deny lists for APIs. IBM COS in our installation lives on a campus network with thousands of untrusted users. Narrowing the scope of networks that can access the manager and data APIs would be helpful in keeping the threat posed by untrusted users accessing an API to a minimum.

Allowing creation of allow/deny lists for access to the manager API and data API, in addition to the included controls on IPs allowed to access vaults, and our own two factor solution for authenticating users would be helpful.
almost 2 years ago in Cloud Object Storage System 0 Submitted

Virginia Tech: Leveraging the built in rsyslog daemon to forward logs is a preferable path for many users (including us!) to avoid having to deploy an external agent. Making sure all COS internal applications log through rsyslog, instead of their own loggers like log4j or other libraries, would be helpful.

It would also be helpful if the COS syslog forwarding options included rsyslog hooks to allow forwarding all logs via insertion of a rule such as "*.* @@customer.log.host"
almost 2 years ago in Cloud Object Storage System 0 Submitted

Virginia Tech: The external agent API endpoint consumes a customer provided tarball, unpacks it and then launches a process using the scripts in the tarball. The tarball is unpacked with whatever file ownership options were passed to tar during its creation. For some applications, this causes problems as the scripts are run as root, but the file ownership is still based on the tar file inputs. The request is to unpack the tarball with customer selectable UGO permissions.

Unpacking the tarball with the appropriate tar flags to ignore the ownership and substitute root or updating the file agent documentation to request the customer producing the tarball use the --owner=root and --group=root options may help customer...
almost 2 years ago in Cloud Object Storage System 0 Submitted

Currently the COS manager application enforces LDAP DNs in strict accordance with the X.500 spec of allowing only OID, C | O | OU | CN as part of the DN. It would aid LDAP integrations if this requirement was relaxed to allow any valid searchable attributes to be part of the DN.

This organization identifies groups by their UUGID, rather than canonical name and relaxing this restriction would allow customers to leverage groups that don't have a traditional X.500 strict DN. I believe this is an X.500 restriction and not nec...
almost 2 years ago in Cloud Object Storage System 0 Submitted

Support more Kafka Authentication Methods

Currently, SASL using plaintext username/password is the only Auth method supported for using the Notification feature in COS. Customers would like to use Kafka's more secure authentication methods. The request is to support all of the auth method...
almost 2 years ago in Cloud Object Storage System 0 Submitted

Ability to split/join storage pools from disparate COS systems

Customers would like to have flexibility with moving/splitting/joining storage pools under the ownership of different COS systems. For example, if a customer must divest a certain portion of data, but the rest, but also keep COS, there is no way t...
almost 2 years ago in Cloud Object Storage System 0 Submitted

When COS has storage pool/access pool communication issue, Event console in Manager GUI might need to keep the record for problematic device name.

When COS has storage pool/access pool communication issue, Manager GUI guide to 'Communication Issues' page, but once the issue is resolved/cleared, we can't know which device had the communication issue. If Event console includes the information ...
about 2 years ago in Cloud Object Storage System 0 Submitted