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,
Post an idea
Upvote ideas that matter most to you
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.
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.
Do not place IBM confidential, company confidential, or personal information into any field.