Cloud Platform
This is an IBM Automation portal for Cloud Platform 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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
I fully agree with this opinion, and I would like to add a few comments.
Container platforms such as Kubernetes are important technologies for enabling a microservices architecture. As systems move toward microservices, CPU resources are assigned to Pods on a per-service basis. However, the current Liberty licensing model does not seem well suited to this approach. This is because Liberty licenses are calculated based on the CPU limit values set for Pods, rather than on the CPU request values or the actual CPU usage.
In practice, a Pod needs a certain amount of CPU just to start, and some extra margin is usually required to handle unexpected situations. As a result, as services are broken down into smaller Pods, the gap between the CPU limit and the actual CPU usage becomes larger. This means that we need to prepare far more Liberty licenses than are actually used, and we are concerned that this may become an obstacle to adopting a microservices architecture.
We truly appreciate the high-quality products and services, including Liberty. We hope that a new user experience better suited to microservices and autoscaling will be offered in the future.