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 (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
Workspace IBM Turbonomic ARM
Created by Guest
Created on Jun 15, 2023

Node state shows as “Active” in Turbonomic Console even when a Node is marked as “unschedulable” in OpenShift

When draining a NODE OpenShift Kubernetes, and un-schedulable in OpenShift, Turbonomic console shows the node as "Active". There is no way to know if a NODE is un-schedulable or cordoned. Similar to VCenter where a Host is in maintenance mode it show inactive in the console. 

Note: NODE was drained and overhead daemon processes were left running. Shows Active.

Idea priority Medium
  • Admin
    Eva Tuczai
    Reply
    |
    Jun 20, 2023

    Hi @David please advise as to the information provided and if this meets the use case, given that State is not exactly the same thing as Status in our Market analysis use of State.

  • Admin
    Eva Tuczai
    Reply
    |
    Jun 16, 2023

    It is important to note that if we use the definition of the entity state (Active, Inactive, Unknown), then this impacts ACTIONS. So if I set a Cordoned node to INACTIVE for example it will block VM Moves, and this is not what you want.

  • Admin
    Eva Tuczai
    Reply
    |
    Jun 16, 2023

    Hi David, active in the market is a definition of an entity. A cordoned node is still running and active. Our analytics understands that the node is not eligible for pods to move there.

    We show NoSchedule which is a k8s taint as part of the "Tags" on a Node. Note this taint is also on control plane / master nodes.

    For visibility, and given that a node can also be un-cordoned so this taint can change, you can create this group. Please see the attached ppt showing you how to do this, that anyone from Turbo can show. Based on this, can we close this Idea as already available?