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.
This issue was also raised by Cathay United Bank(Taiwan) as they executed the scaling action for AWS EMR node and it failed as the instance type recommended by Turbonomic was not a supported instance in AWS EMR.
Have asked the customer to upvote this and as a workaround, To avoid any scaling action from being recommended by Turbonomic, we advised the customer to create a VM group containing EMR clusters and disable Cloud scale all action for this VM group.
What is the added value in your opinion to add this feature to Turbo? What are the savings you would be looking at if this happens?
What is the cloud spend?
What are their pain points?
We would like to understand what we can solve if we add this feature?
Short answer: No, Turbonomic cannot optimize EMR clusters directly (it doesn’t model EMR as a first‑class object). Yes, you can safely optimize EMR indirectly by letting EMR manage the cluster semantics (node counts, lifecycle) while Turbonomic manages the underlying EC2/EBS/ASG resources with the right guardrails. And since turbonomic already takes care of the underlying resources I am not sure we should even consider doing this right now…