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,
Post an idea
Upvote ideas that matter most to you
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 notifications 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.
Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):
Cloud Pak for Multicloud Management
Cloud Pak for Network Automation - incl Orchestration and Performance Management
Cloud Pak for Watson AIOps - incl Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - incl IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - incl Workload Scheduler
Tivoli System Automation - inc Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
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: https://examples.openshift.pub/networking/egress-ip/.
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.
Why is it useful?
It allows more sensible security concepts and lowers work for network and security teams.
Do not place IBM confidential, company confidential, or personal information into any field.