Goal

Today the UI is responsible to identify mismatches between the VM and VMI definitions and notify the user that they need to restart the VM for the changes to take affect. As we are enhancing our hot-plug capabilities and enable applying some of the changes using LiveMigration or no operation at all (like once Multus 4 will be introduced to OCP), the logic of when a restart is required vs. a LiveMigration (or something else) should be done by the backend and not the UI.

This also applies to future work we may do to support things like modifying labels, node selectors etc.

Doing so in the backend should also raise an alert with the operation the user need to perform in order to apply the change, and that's regardless if they are using the UI or CLI

User Stories

• As a UI developer I do not want to understand the backend dependencies on what operation is required to apply each change, as this vary between the what was changed and different versions
• As a UI developer I don't want to keep track of new capabilities from the backend and keep adding new ones to logic that is done in the UI
• As a backend developer that is working on hot-plug enhancements, I already know what is required to apply the change and just need a way to notify the user about it
• As a user I would like to get notified on what operation should I perform in order for my change to be applied even when making the change using the CLI

Non-Requirements

Notes

• The responsibility of checking any VM to VMI mismatch should be removed from the UI and move to the backend. We can use the existing mechanism to create alerts that can also be displayed in the UI