IBM PowerVM is the best and most stable product in the virtualization market. It gives the best performance with IBM Power Server, especially its best solution, where we have to run critical applications and save applications licensing costs. It provides a lot of good features …
IBM PowerVM only is available on IBM POWER machines. It makes live much easier, compared to bare metal machines (OPAL) or machines with KVM. Personally I would not like to manage systems that don't have IBM PowerVM. The current line-up always includes IBM PowerVM (firmware built-in).
K8s should be avoided - If your application works well without being converted into microservices-based architecture & fits correctly in a VM, needs less scaling, have a fixed traffic pattern then it is better to keep away from Kubernetes. Otherwise, the operational challenges & technical expertise will add a lot to the OPEX. Also, if you're the one who thinks that containers consume fewer resources as compared to VMs then this is not true. As soon as you convert your application to a microservice-based architecture, a lot of components will add up, shooting your resource consumption even higher than VMs so, please beware. Kubernetes is a good choice - When the application needs quick scaling, is already in microservice-based architecture, has no fixed traffic pattern, most of the employees already have desired skills.
IBM PowerVM is used for virtualization on IBM Power series hardware to utilize the hardware resources more efficiently like micro partitioning for CPU, NPIV for fibre port...etc
IBM PowerVM provides the feature of live partitioning mobility (LPM), which allows moving the running virtual machine from one hardware to another hardware without any disruption on a virtual machine.
IBM Power VM provides the feature of Integrated virtual manager (IVM), which helps to manage the single IBM Power hardware. There is no need to purchase a separate hardware management console to manage the Power hardware. This works well for small organizations having small environments.
Local development, Kubernetes does tend to be a bit complicated and unnecessary in environments where all development is done locally.
The need for add-ons, Helm is almost required when running Kubernetes. This brings a whole new tool to manage and learn before a developer can really start to use Kubernetes effectively.
Finicy configmap schemes. Kubernetes configmaps often have environment breaking hangups. The fail safes surrounding configmaps are sadly lacking.
The product works. It provides the proven environment to support IBM's primary operating systems that run on the IBM Power processing systems. This by extension includes the IBM various storage products that work within that environment. It has proven to be seamless as the environment has grown and as various new products and version updates have been added. As with most IBM products, the support is excellent.
The Kubernetes is going to be highly likely renewed as the technologies that will be placed on top of it are long term as of planning. There shouldn't be any last minute changes in the adoption and I do not anticipate sudden change of the core underlying technology. It is just that the slow process of technology adoption that makes it hard to switch to something else.
Since it is built into the firmware (hardware) it requires no separate installation (except for the Virtual I/O servers, if you need those). Both HMC and Novalink (with PowerVC) support IBM PowerVM well and offer a user-friendly interface to setting up LPARs and making changes, most on the fly. Modern systems also give insights into performance, power consumption etc. A lot of separate tools exist to show more details, like LPAR2RRD, IBM Instana, IBM Turbonomic etc.
It is an eminently usable platform. However, its popularity is overshadowed by its complexity. To properly leverage the capabilities and possibilities of Kubernetes as a platform, you need to have excellent understanding of your use case, even better understanding of whether you even need Kubernetes, and if yes - be ready to invest in good engineering support for the platform itself
Our company utilizes VMware and PowerVM. VMware is very user friendly from an IT support view and makes supporting Windows OS easier. PowerVM is moving in that direction. PowerVM is better in that you can prioritize workloads across different VMs and be granular in your reservation of cores and virtual CPUs. PowerVM allows you to modify VM characteristics while the VM is up and running
Most of the required features for any orchestration tool or framework, which is provided by Kubernetes. After understanding all modules and features of the K8S, it is the best fit for us as compared with others out there.
We are able to run several LPARs on one frame, which means we do not need to buy as many physical servers. That saves on floor space, power, and heating and cooling of the data center, among other things.
Using LPM allows us to do maintenance on a frame without impacting the LPARs, giving us greater uptime.
