Skip to Main Content
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 (

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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Created by Guest
Created on Jul 27, 2022

Eliminate updates to plugins when using Workload Mobility

When creating Virtual System Patterns (VSPs), clients can opt to lock the system plug-ins as documented in the section "Lock option for plugin usage" here.

Clients who deployed Virtual System Instances (VSIs) using Virtual System Patterns that had "Lock option for plugin usage" set to "Unlock plugins" might face some challenges when using Workload Mobility to move those VSIs to another IBM Cloud Pak System. Specifically, the new VSI on the target IBM Cloud Pak System will automatically update all plugins associated with that VSI to the latest version available on the target IBM Cloud Pak System. This results in python code corresponding to those plugins to get updated on the Virtual Machines (VMs) corresponding to the VSI. While differences between plugin versions and their python code are typically small, they do change data on the VMs. However in some cases, the changes are not compatible with the VSI and can lead to middleware roles and services on the VMs of the VSI on the target IBM Cloud Pak System not reaching a RUNNING state (and the VSI as a result would also not reach RUNNING state).

Today IBM recommends to only use VSPs using "Lock option for plugin usage" set to "Lock all plugins" when using Workload Mobility to move the VSIs deployed using those VSPs. That avoids the update of plugins of the VSI as a result of using Workload Mobility. However we believe it would be better if the Workload Mobility feature of IBM Cloud Pak System would ensure that no plugins would get updated, regardless of what "Lock all plugins" was set to in the VSP used to deploy the VSI. This could for example be achieved by introducing a supported mechanism to change an existing VSI such that it would behave as if it was deployed by a VSP using "Lock option for plugin usage" set to "Lock all plugins".

Idea priority High