Skip to Main Content
IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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 17, 2023

Please add a pod anti-affinity preferredDuringSchedulingIgnoredDuringExecution constraint to the build configs that get generated by Manage

When Manage is deployed with separate cron, mea, report and ui bundles the cron-build, mea-build, report-build and ui-build are started concurrently after the admin build.

Our observation is that in OCP 4.12 these 4 builds usually get scheduled on the same worker node at the same time. Next, all 4 builds fail with a no space left on device error message; the worker node the builds got scheduled on just did not have enough space for ephemeral storage (200 GB is not enough). These builds do need a lot of storage.

Please add a pod anti-affinity preferredDuringSchedulingIgnoredDuringExecution constraint to the build configs that get generated by Manage to have these builds scheduled on different worker nodes where possible.

Idea priority Medium
Needed By Yesterday (Let's go already!)
  • Admin
    Jenny Wang
    Reply
    |
    Oct 17, 2023

    Manage leverages OpenShift BuildConfig. It only supports nodeSelector, not preferredDuringSchedulingIgnoredDuringExecution. Manage supports specifying amphoral storage request and limit for Manage admin build and bundle build. The user should be able to specify a large value, so that the scheduling of the build pod will assign the work into the nodes that have sufficient storage.

    What is lacking is cpu, resource, nodeSelector is currently not specifiable on the ManageWorkspace CR. However, the user can manually change the BuildConfig to specify those, and they won't be overwritten until ManageBuild CR is deleted.

    1 reply