Cloud Platform
This is an IBM Automation portal for Cloud Platform products. 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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
This IDEA was delivered in our 8.0.1 release in March of 2024.
This idea is planned to be delivered in the 8.0.1 release in March, 2024.
Hi Edward, this IDEA is "in development" and is currently marked for the April 2024 release. Thank you!
Hi Edward, here is our implementation plan for this Idea. Could you review this and give us your feedback?
Below is the implementation plan for this RFE.
"Set agent to Unavailable:
agent pools will not select unavailable agents
running processes that have already resolved the agent will be able to send steps to the agent
new processes that attempt to resolve this agent will fail as the agent is unresolvable."
Hi Edward,
We spoke with the development team and their response can be found below:
"Ok, so we have more questions for you about how robust this should be. But before that we want to try reframing this:
What if we instead make this an agent pool feature? So you can't put agents in maintenance mode but you can do maintenance on agents in an agent pool? Perhaps a checkbox on each agent that says "Ignored by agent pools". If checked that agent will not be selected from any agent pool. However, the agent could still be used directly such as running a generic process specifically on that agent.
The question we had about the robustness was:
If you have an app deployment that runs a component process that runs another app deployment. Can that second app deployment run or should it not? That is harder to implement than allowing a single process to finish."
We have some questions for you:
Do they want the agent to be used in process if the process had already resolved that agent?"
If an agent has been used in a component process and that agent could be used later in another component process should that work?
If an agent has been used in a component process would ongoing work by that agent fail? If it isn't supposed to fail, would future plugin steps in the same component that use that agent succeed or fail?
Thank you for submitting this RFE. We are creating an internal discussion topic with the development team to discuss this request. I think it is a good idea. It is like a "maintenance mode" feature for the UCD Agent (as opposed to what we have today for the UCD Server). We will be in touch. Thanks again!