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

Cloud Object Storage System

Showing 22 of 5218

Network option for Ceph Ready Nodes

Our customers have asked us to upgrade their network performance and availability for Ceph Ready Nodes. Therefore, we would like you to add networking options as well as disk drives. - Number of NIC ports. Currently, with only two ports(10GbE), cu...
6 months ago in Cloud Object Storage System 0 Submitted

Swagger support for REST APIs

Add support for Swagger so that COS devices and config can be integrated with Swagger.
8 months ago in Cloud Object Storage System 0 Submitted

Certificate key authentication supported for SFTP log transfers

Customer would like to use an SSL Public Key option for the configured SFTP connection in the 'Settings--Support--Logs--Log Collection--Log Collection Configuration--Log Destination' Log Collection Configuration page. There is an SSL/TLS certifica...
about 1 year ago in Cloud Object Storage System 0 Submitted

S3 to Tape

Provide a mechanism to flush out/tier older objects at bucket level from COS to tape ideally while preserving some kind of object level reference in the source bucket not having to rely on data movement at the application layer or leverage the COS...
about 1 year ago in Cloud Object Storage System 0 Submitted

Container Mode support for embedded accessers

with the new AWS S3 Object Lock functionality we're opening tons of new use-cases to COS. this is great! unfortunately S3 Object Lock is only supported on container modes, not vault modes. smaller COS systems with embedded accesser configs are lim...
about 1 year ago in Cloud Object Storage System 0 Submitted

Manager database backup to a Cloud bucket - adding custom CAs

The COS Manager database backup to a Cloud bucket feature needs some enhancements. Today you can configure the Manager database backup to an S3 bucket using either the Manager UI or the REST API with any HTTPS endpoint using a certificate issued b...
about 1 year 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.
about 1 year 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"
about 1 year 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...
about 1 year 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...
about 1 year ago in Cloud Object Storage System 0 Submitted

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.