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
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.
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.
Thank you for taking the time to provide your ideas to IBM. We value our relationship with you and appreciate your willingness to share details about your experience, your recommendations, and ideas.
The partial solution previously discussed was impractical to implement. We do not see a practical way of addressing this requirement. We will be rejecting this Idea at this time. If you would prefer that IBM re-evaluate this decision, please open a new Idea.
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.
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
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?