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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):
Cloud Pak for Multicloud Management
Cloud Pak for Network Automation - including Orchestration and Performance Management
Cloud Pak for Watson AIOps - including Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
IBM Turbonomic ARM
ITM-APM Products - including IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - including Workload Scheduler
Tivoli System Automation - including Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
Constrained vCPU VM's from Azure taken into consideration for recommendations
Azure has a class of VM's that have constrained vCPU's for DB vm's that often require high memory, storage and IO bandwidth, but not high core count. So the VM class will basically only use a portion of the core count for that class to save money on SQL licenses. Azure is kinda dirty, as they don't offer a lower cost for this class of VM, so the only savings is for licenses. In the case of my customer, they have purchased VM's from Azure using the VM class Standard_E64-16s_v3, which only utilizes 16 cores, but has all of the other resources that would go with a 64core VM. It does not appear we take these VM classes into consideration, as we are recommending that they move this vm to the regular Standard_E64_v3 because how we see it, for the same cost, you go from 16 cores to 64 cores. Well yes, that is true, but now you are paying so much more for SQL licensing. All of this being said, perhaps this is something we should look into for our product. I have already spoken to AJ about this and he told me to submit an ER. https://docs.microsoft.com/en-us/azure/virtual-machines/constrained-vcpu
Do not place IBM confidential, company confidential, or personal information into any field.