Description of problem:
oVirt Node is going to switch to a new TUI which changes the way how the UI is specified.
VDSM's page for ovirt-config-setup needs to be updated to be usable by the new TUI.
An example page which mimics the old TUI page can be found in this commit and can be used as a starting point.
The following patch adds logic to the new engine page (currently hosted in ovirt-node)
Most functions could be resued, except the central logic (action()), this couldn't directly be wrapped, because it relies on informations from the snack ui (which has been removed). This page should be merged back into vdsm on the long term.
The current implementation has the limitation that it's not interacting with the UI (so the user can currently not directly confirm the fnigerprint), I'm looking for a solution for this, which will hopefully land during the beta phase.
The engine page got migrated and already removed from Nodes codebase again,
this patch should still go into the page: