packaging: services: prepend pythonlib

devenv should shadow default search path, so system library will not
shadow devenv.

Change-Id: I5383c6529e822d92593d2e915a76bc3b25855866
Signed-off-by: Alon Bar-Lev <alonbl@redhat.com>
packaging: spec: always pull recent pythonlib

Change-Id: I113dd0a5bb477b02d857dcca820fd2a2a8b54762
Signed-off-by: Alon Bar-Lev <alonbl@redhat.com>
packaging: detect java home at runtime

CURRENT IMPLEMENTATION

detect java home during installation.

advantage is optimize application execution post-setup.

disadvantage is that java home may be altered by system updates.

NEW IMPLEMENTATION

detect java home during runtime using pre-defined algorithm.

algorithm:

execute /usr/share/ovirt-engine/bin/java-home.

if java-home.local is available, execute that script. this enables
distro specific customization.

if OVIRT_ENGINE_JAVA_HOME environment is set, validate java validity
and use/abort.

search predefined selected alternatives location by order, first wins.

search /usr/lib/jvm for compatible jvm.

NOTES

the java-home script resides with the lib package as it cannot reside
within any version locked package since it is used by setup, and it
cannot reside within setup since it used by post setup.

Bug-Url: https://bugzilla.redhat.com/show_bug.cgi?id=1009863
Change-Id: I833362d0498d534b06e0d7660f1e8a61e9b1713b
Signed-off-by: Alon Bar-Lev <alonbl@redhat.com>
webadmin: Replaced null profile with empty profile

Added a special value to represent an empty profile, and changed empty
profile instances to that instead of null. This is needed by a
soon-to-be-implemented Add/Remove VNIC widget in the Add/Edit VM
dialog, in order to discriminate between the case where a profile
hasn't yet been assigned (null) and the case where the empty profile
has been assigned (VnicProfileView.EMPTY).

Change-Id: I06962e43084ff4fd469e0025527cdd85a47f5ea7
Signed-off-by: Lior Vernia <lvernia@redhat.com>
webadmin: Unified VNIC update logic on VM creation

Towards adding the ability to add and remove VNICs in the add/edit VM
dialogs, the VNIC logic is unified so it is the same for all kinds of
VM creation flows (e.g. from scratch, from template...); VNICs may
always be added, edited or removed.

Change-Id: Ifbd61031572a3462af46f24c64fb5bb80343f086
Signed-off-by: Lior Vernia <lvernia@redhat.com>
webadmin: Introducing AddRemoveRowWidget

This is a reusable widget used to display a list of other widgets,
backed by a ListModel of values. Entries may be removed or added using
minus/plus buttons. A new entry is added by activating a semi-disabled
"ghost" entry.

Change-Id: I15958e4b7c1fcf0ec08ea35eb32c690964f2a366
Signed-off-by: Lior Vernia <lvernia@redhat.com>
webadmin: Add/Remove VNICs in Add/Edit VM dialog

Enabled adding/removing VNICs in the VM dialogs using
AddRemoveRowWidget.

Change-Id: Id7654d137541aec64ce19aa309021b307253171e
Signed-off-by: Lior Vernia <lvernia@redhat.com>
webadmin: Don't add VNICs to a VM by default

VNICs used to be added to VMs created from VNIC-less templates by
default, to accommodate assigning some sort of network connection to a
VM when creating it. This is no longer needed, as VNICs can now be
added and removed by the user in the same dialog.

Change-Id: I2d00fd6a4fb280d9604bc1ae586fcc588d4a7196
Bug-Url: https://bugzilla.redhat.com/1003779
Bug-Url: https://bugzilla.redhat.com/1009298
Bug-Url: https://bugzilla.redhat.com/1010856
Signed-off-by: Lior Vernia <lvernia@redhat.com>