Hide Forgot
Description of problem: Currently the ui plugin resides in the same package as the cockpit plugin. It would be good for shipping and code separation reasons to split this part into a separate package.
What actual issue does it cause?
Mainly packaging reasons: The ui plugin does not share any code with the cockpit bits. For easier packaging and an easier release process it would be good to separate them.
it can be removed in 4.2, replaced with proper subtab directly in engine code
(In reply to Michal Skrivanek from comment #4) > it can be removed in 4.2, replaced with proper subtab directly in engine code QE need to clarify that there will be no cockpit-ovirt-uiplugin.noarch package, and will find such "cockpit" tab on ovirt-engine webadmin directly, right?
yes, there will be no such package. However whether there will be a subtab or a different way how to open cockpit is to be decided. It was suggested to replace that with a hyperlink opening new window with cockpit, or a menu item in Hosts main tab to do that. Adding Sandro to share his thoughts since cockpit interface is mandatory for node configuration now
(In reply to Michal Skrivanek from comment #6) > yes, there will be no such package. > However whether there will be a subtab or a different way how to open > cockpit is to be decided. It was suggested to replace that with a hyperlink > opening new window with cockpit, or a menu item in Hosts main tab to do > that. Adding Sandro to share his thoughts since cockpit interface is > mandatory for node configuration now Not sure what's the question here. This bug is just moving the engine ui plugin for cockpit out of cockpit-ovirt to its own git repo. The design of the UI plugin itself should be discussed in a RFE or in devel mailing list I think. On my side I've no strong preference on its implementation.
we'll drop the plugin and replace with a better suited solution. tracked in https://trello.com/c/UrPaq9Oo