IBM Data and AI Ideas Portal for Customers

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:

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

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Future consideration
Workspace Spectrum LSF
Components Scheduling
Created by Guest
Created on Jan 12, 2021

Add support to Kerberos ticket with new "renew-until" date for already submitted jobs

While using Kerberos ticket forwarding on a LSF cluster:

Currently TGT found on the submission host is copied to LSF cache and forwarded to the execution host at job submission; These tickets can be renewed automatically by LSF until the TGT "renew-util" date is reached.

This behaviour could introduce some issues for long-pending or long-running jobs on the clusters, especially in case the Kerberos tickets management system is a corporate service that could not be easily tuned for HPC purpose.

Proposal: Let LSF check for new TGT on the submission host for already submitted jobs - and update the cached TGT when applicable; Users and/or administrators could then manage to update TGT on the submission host, and LSF would propagate the new ticket to existing pending and running jobs.

This would be highly valuable to get rid of this "renew-until" limit.

  • Guest
    Mar 3, 2021

    Olivier, we've added this to our backlog, and will get to it when resource becomes available. Unfortunately I am not able to give a definitive time frame at the moment.

  • Guest
    Jan 18, 2021

    Thanks for your feedback;
    Yes I assume that even a partial solution would make sense;
    Updating the TGT for pending jobs would anyway reduce the risk to reach the renew-until limite date during computations.
    Best regards,
    O. Moritz

  • Guest
    Jan 17, 2021

    It is plausible to add an option to update the TGT for a pending job.
    However, once a job starts, there is no way in Kerberos to update the TGT.
    So we could only partially address the requirement in this RFE, is a partial solution useful?