Skip to Main Content
IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


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.

IBM Employees should enter Ideas at https://ideas.ibm.com


Workspace Planning Analytics
Created by Guest
Created on Apr 10, 2024

Planning Analytics Workspace (PAW) on OpenShift: Implement MySQL as StatefulSet

The issue with the MySQL in PAW is that it is implemented as Deployment. When the database pod is rescheduled, there is a chance that the new instance is started before the old instance has finished shutting down. In this situation, both pods write to the share and tha database is corrupted.

This happens mainly during cluster upgrades or machine config deplyoments, when nodes are cleared in order to be updated.

The issue is resolved when the database is configured as a StatefulSet, as a new instance is guaranteed to be started only after the first one has shut down completely.

RedHat confirms that this is best practice for databases in OpenShift.

Needed By Week
  • Admin
    Stuart King
    Reply
    |
    May 22, 2024

    Updated status to 'In development'. Delivery is planned for Q3 2024.