Integration

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

Start by posting 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 offering manager 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 a 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.

If you encounter any issues accessing the Ideas portal, please send email describing the issue to ideasibm@us.ibm.com for resolution. For more information about IBM's Ideas program visit ibm.com/ideas.

Status Under review
Workspace Aspera
Created by Guest
Created on Nov 23, 2021

Orch - Resource/Load Manager does not allow view/list tokens used by a resource

Resource and Load Manager Plugins have no way to see what tokens are taken by what workflow or process/token name. If they go stale or fail/bad, the resource pool cannot be managed.

Idea priority Medium
Why is it useful?

Think of old bank teller windows. You have 5 tellers each with a capacity of 2. Wouldn't you want to know who was holding those tellers up in case in case they stalled for a bad ATM card or something else? This way the token could be dynamically reassigned instead of tossed back into the queue (which is what I do today on a resource timeout, but the resource does not time out since the transfers can be hours or days long). I've tried 10 other ways to do this, but direct reporting of tokens in use by Orch makes the most sense.

Use Case - As a resource admin, my application needs to know who owns what resource in the pool. WO and token name are required. This way, I can manage the resource pool timeouts externally versus using simple hold timeouts. Like Queues, WO failures holding tokens need to remove those tokens automatically.

Who would benefit from this idea? Infrastructure owners using limited or costly compute capacity.