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,
Post an idea
Upvote ideas that matter most to you
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
See this idea on ideas.ibm.com
We need a product enhancement to support no down time during the OpenShift maintenance. OpenShift maintenance typically requires node restart. If DataStage PXRuntime pods were running on those worker nodes, the jobs will fail.
If we have a control over where (which pods) the incoming jobs should be dispatched, we can avoid the pods on the worker that needs to be put in maintenance, and wait for the pods on that worker to complete all jobs. Then, we can shutdown the target worker nodes safely without having to aborting the jobs.
To accomplish this,
•Requires a new capability to mark the POD to not dispatch any more OSH tasks.
•The PODs with this flag continues running existing tasks but not new ones after being marked as “maintenance”.
•The jobs on those POD will finish the process and eventually the POD will drain out all OSH processes.
•Also need helper commands:
•get-pod-maintenance, set-pod-maintenance, unset-pod-maintenance, list-jobs-on-pod, etc
Please see the attached document for more details.
Needed By | Month |
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.