Skip to Main Content
Cloud Management and AIOps


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).

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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. 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.

Status Functionality already exists
Created by Guest
Created on Jun 25, 2024

Set workflows to run on all workers in a worker pool

It would be useful to be able to set a workflow to be executed on every worker in a worker pool, rather than round robin. This is useful for testing type scenarios when I'd want to run the same test from multiple endpoints and collate the results. In addition, it would be a bonus if we could slim down the remote workers (or offer a remote worker lite option with reduced capabilities) so we could deploy many many remote workers on a light footprint.

Idea priority Low
  • Admin
    Shane Hadden
    Reply
    |
    Oct 17, 2024

    Remote worker groups are intended to be used to provide scale and redundancy within a specific zone. The worker group is the mechanism for controlling the execution location for the flow. A typical remote worker setup would use a worker group per zone, area or security context. (E.g. Arizona would be one group with multiple workers, and Chicago and New York would be separate groups with their own workers)

    If flow execution from multiple zones is required, each zone should have its own worker group. Workflows can then be written to execute actions in different worker groups to accomplish business processes as needed across those separate zones.

    Here's an example flow that would ping a specified IP from each worker group: