Description of problem: When Node is beeing managed by e.g. oVirt Engine it should prevent the user from change e.g. the Network configuration as the network configuration is done by Engine/VDSM. Additionally it might make sense if the management instance told Node's TUI what interface the primary interface is so the TUI can display live informations about the NICs. I'm suggesting the following keys which are shared by Node and the management instance to exchange relevant bits: OVIRT_MANAGED_BY=<vendor> This key is used to (a) signal the Node is being managed and (b) signaling who is managing this node. OVIRT_MANAGED_IFNAMES=<ifname>[,<ifname>,...] This key is used to specify a number (comma separated list) if ifnames which are managed and for which the TUI shall display some information (IP, ...). This can also be used by the TUI to decide to not offer NIC configuration to the user. OVIRT_MANAGED_LOCKED_PAGES=<pagename>[,<pagename>,...] (Future) A list of pages which shall be locked e.g. because the management instance is configuring the aspect (e.g. networking or logging).
Douglas, currently the ovirt node tui can only display reliable network informations when the network got configured by the tui. When vdsm is taking over the network configuration the tui displays incorrect informations (on the status page). To improve the situation we need to sync the network informations (and maybe others) between the tui and vdsm. My suggestion is to use some keys which vdsm can use to tell the tui about the e.g. primary NIC (some brige, ovs ...) to display a summary about.
Hi Fabian, Make sense. However, for this specific network point, better include vdsm network folks into this thread.
I've stated my opinion in http://lists.ovirt.org/pipermail/arch/2013-October/001688.html I see the merit of locking network tui after registration (provided that there's a means to unlock it), but not much of the rest.
This is an automated message. Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.
Due to some changes we didn't take care of Node bugs. This will get better. This bug is actually fixed already.