This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
See this idea on ideas.ibm.com
Would like to see if there might be a way to force sizing actions when needed . Have several situations where we want to do **non-usage based sizing** what I call = "planning sizing" . Use cases are - where app owners have done load testing and knows the load is coming to the app instance and wants to size "in mass" to proactively size the app instance for upcoming load. There are allot of different use cases for this type of sizing.
Just thinking through the UI and how we might be able to do this is in policies have that have a "ignore usage and market" toggle on the policy.
Current support ticket we review these type of use cases with - TS015514933
Bug # = TRB-80250
Idea priority | Low |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Have a use case now where they want to add CPU's b/c during their peak time CPU usage got high/topped out. Been forcing sizing for some time now. Typically, I can make them happen by tweaking the policies. Thats all time I don't want to spend/wasting "forcing" these actions. Would like to propose that you make the Minimum settings hold true = if I set a minimum, for CPU or RAM it should give me an action to move to that minimum, otherwise there is no point to the minimum setting in Turbo policies, plus if you made the min "rule supreme" (as they should imo) Then you would have forced sizing an option in the product while making the minimum values act as they should . Would assume this option would cut down development time quite a bit from any other options.
Love it!
Also opened up support ticket = TS016391033 for this (above use case).
Have a use case I'm working on , where we have the actions close to what we want. Still have 2 actions in the list (CPU actions) that want to size up from 2 to 3 CPUs, and all policies related to the actions should be 2 to 4 CPU's . Would like to present as use case for this .