Skip to Main Content
Integration


This is an IBM Automation portal for Integration 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 Under review
Created by Guest
Created on Oct 24, 2022

Tolerance and node-selector support for ACE IS CR

In order to optimise license costs, today ACE IS (Integration Server) pods on CP4I on Openshift run on dedicated worker nodes so that the license cost amounts to the worker node capacity.


We have implemented this using node-selectors on the openshift namespace where ACE pods run. But the issue is other non-ACE pods continue to be scheduled on ACE worker nodes reducing the total available CPUs for ACE.


As per REDHAT the only way to prevent this is to have taints on the worker nodes and then set a corresponding toleration for the taint + node-selector label on the application which in this case amounts to the ACE IS CR/ACE operator is what we think.


These are some examples on how these configs can be applied on application objects just to give an idea:

https://docs.openshift.com/container-platform/4.10/monitoring/configuring-the-monitoring-stack.html#moving-monitoring-components-to-different-nodes_configuring-the-monitoring-stack

https://docs.openshift.com/container-platform/4.10/monitoring/configuring-the-monitoring-stack.html#assigning-tolerations-to-monitoring-components_configuring-the-monitoring-stack

Idea priority Urgent
  • Admin
    Andy Garratt
    Oct 31, 2022

    Hi Abu - thanks for coming back on this - will check in again with James.

  • Guest
    Oct 28, 2022

    Hi Andy,

    The doc you linked is for setting up node-selectors using labels as far as I can tell. This will not solve the problem as we are already doing this today. We should in addition to node-selectors, also be able to set "tolerances" to counter the taints on the ACE's worker node which is not possible today in the ACE Operator framework. Could you please have a dialogue with James too? I had discussed with him before raising this RFE.

  • Admin
    Andy Garratt
    Oct 28, 2022

    Hi Abu,

    Thanks for raising this - can you review the attached docs here and see if this helps with what you're wanting to achieve? https://www.ibm.com/docs/en/cloud-paks/cp-integration/2022.2?topic=planning-node-placement-considerations

    Please let us know so we can progress the idea appropriately.