Skip to Main Content
Cloud Management and AIOps

This is an IBM Automation portal for Cloud Management 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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Created by Guest
Created on Jul 1, 2021

Allow usage of namespace egress IPs in NOI on OCP installations

Our customer is extending their Netcool landscape to integrate several existing sites into one centralized NOI based on OCP. Actually there are various components within NOI on OCP, that need to connect to these already existing sites. Some examples of such components are DASH for event federation, MessageBus GW and NOIActionsService for Event Analytics, ASM Observers to local ITNM installations and RBA components to run actions locally. All of these components run on pods, that may be located on every worker node. So connections need to be allowed from all worker nodes to all existing sites. And if new worker nodes are added to OCP, they also need to be included in such connection rules.

It would be much better to have a kind of loadbalanced IP for each of these components running in OCP. There is a concept called namespace egress-IP for this. A matching using example for this is described here:

But actually Cloud NOI doesn't support this feature.

The installation possibilities of NOI should be enhanced to support such a feature to ease the definition of communication rules to lower work on firewalls and routing.

Idea priority High
  • Guest
    Jul 2, 2021

    I think this is a very useful and practical enhancement, also when it comes to integration of Watson AIOps and existing Netcool environments.