This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Nicolas, I'd like to explore alternative solutions because I'd prefer to avoid enabling users to turn off automatic SelfMon device creation.
Here's some follow-up questions aimed at better understanding:
Are these net new peers you're adding to a cluster, or are you taking a base image and doing an HSA add to replace a retired node?
Do you delete self-monitoring devices and re-create them with your PAVE/REPAVE functions? I'm trying to figure out why new SelfMon devices are created in the first place.
What prevents devices added by other means from blocking the repave automation?
Is the problem that the new SelfMon device is in the queue for first discovery, or that its active discovery blocks your automation from working properly due to device locks?
If it were possible to cancel all running discoveries and prevent new discoveries from starting until discovery was re-enabled, would this help?
If there are any other mechanistic details you can share about how device discovery or the new SelfMon device creation blocks your automation, please do.
I'm also open to chatting via a video call if you feel that would be more productive.
Ryan Wilson
Senior Product Manager, IBM SevOne
ryan.wilson4@ibm.com