Hi Leni, On Tue, Apr 25, 2017 at 10:45 AM, Leni Kadali Mutungi <lenikmutungi(a)gmail.com&gt; wrote: My recommendation is save the output of 'sudo make install &> /tmp/output-make-install-otopi' and debug it, start checking if the path of destination files are correct. Not sure if this your case, but, I have noticed some similar errors when --prefix is not set. """ By default, `make install' will install all the files in `/usr/local/bin', `/usr/local/lib' etc. You can specify an installation prefix other than `/usr/local' using `--prefix', for instance `--prefix=$HOME'. """ For this case, I would suggest try: ./configure --enable-java-sdk --with-maven --prefix=/usr/ Fell free to share with us the output of make install. Thanks Douglas -- Cheers Douglas

On Tue, Apr 25, 2017 at 7:45 AM, Leni Kadali Mutungi <lenikmutungi(a)gmail.com&gt; wrote: On debian testing, I managed to build and install using ./configure --with-otopi-sources=/root/otopi (this is where I'd checked out and built otopi) I got this error running ovirt-host-deploy: # ovirt-host-deploy ***L:ERROR Internal error: Internal error, plugins set(['otopi', 'ovirt-host-common', 'ovirt-host-deploy']) are missing It ran a bit further when run from the source dir: # ./src/bin/ovirt-host-deploy [ INFO ] Stage: Initializing Continuing will configure this host for serving as hypervisor. Are you sure you want to continue? (yes/no) yes [ INFO ] Stage: Environment setup Configuration files: [] Log file: /tmp/ovirt-host-deploy-20170425170102-6mdsx6.log Version: otopi-1.7.0_master () Version: ovirt-host-deploy-1.7.0_master () [ INFO ] Stage: Environment packages setup [ ERROR ] Failed to execute stage 'Environment packages setup': Packager install not implemented [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination

On Tue, Apr 25, 2017 at 10:27 PM, Leni Kadali Mutungi <lenikmutungi(a)gmail.com&gt; wrote: Are you (both Leni and Jason) trying to make otopi/ovirt-host-deploy build/install/run from a "dev-env" (non-root), or are you trying to package them for debian? otopi checks for plugins in its env under key BASE/pluginPath. If running from either source (as above) or a bundle (see README.API, this is actually needed for ovirt-host-deploy to work in its expected normal flow), it has special code for setting it. Otherwise it defaults to $(pkgdatadir)/plugins , where pkgdatadir is set by autoconf (and defaults to $PREFIX/share/otopi. So if you want 'dev-env', pick a prefix (say, ~/ovirt-stuff), build everything with the same prefix, and add $prefix/bin to your path. If you want to package for debian, you should mostly use debian defaults for most things imo. Best, -- Didi

Sorry for the silence. I've been doing some tinkering. I did what Jason did i.e. `./configure --enable-java-sdk --with-maven --with-otopi-sources=/home/user/otopi` since that's where I had checked out otopi. ./configure is able to locate where the otopi-bundle file is (/usr/share/otopi directory for me) with the options above. If you try to use the options `--otopi-bundle` or `--with-otopi-bundle`, you'll get a unrecognized option from ./configure. I then ran `sudo ovirt-host-deploy/src/bin/ovirt-host-deploy` at my command prompt and got the same error as that which Jason got. Difference being that I wasn't doing the compilation as root, I was using sudo for elevated privileges. Looking at the log file, I saw the following errors: 2017-05-07 07:21:37,011+0300 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpackager._boot:184 Cannot initialize miniyum Traceback (most recent call last): File "/home/user/otopi/src/bin/../plugins/otopi/packagers/yumpackager.py", line 176, in _boot self._refreshMiniyum() File "/home/user/otopi/src/bin/../plugins/otopi/packagers/yumpackager.py", line 134, in _refreshMiniyum constants.PackEnv.YUM_ENABLED_PLUGINS File "/home/user/otopi/src/bin/../plugins/otopi/packagers/yumpackager.py", line 61, in _getMiniYum from otopi import miniyum File "/home/user/otopi/src/otopi/miniyum.py", line 17, in <module> import rpmUtils.miscutils Traceback (most recent call last): File "/home/user/otopi/src/otopi/context.py", line 132, in _executeMethod method['method']() File "/home/user/ovirt-host-deploy/src/bin/../plugins/ovirt-host-deploy/vdsm/vdsmid.py", line 84, in _packages self.packager.install(('dmidecode',)) File "/home/user/otopi/src/otopi/packager.py", line 98, in install raise NotImplementedError(_('Packager install not implemented')) NotImplementedError: Packager install not implemented So as a workaround, I used the instructions in the README to create a file called /etc/ovirt-host-deploy.conf.d/50-offline-packager.conf to suppress this reaction. Contains the following instructions: [environment:init] ODEPLOY/offlinePackager=bool:True PACKAGER/yumpackagerEnabled=bool:False This allowed it to run further than it did for Jason (and myself when I tried it out). The new error message I got was: user@localhost:~$ sudo ovirt-host-deploy/src/bin/ovirt-host-deploy [sudo] password for user: [ INFO ] Stage: Initializing Continuing will configure this host for serving as hypervisor. Are you sure you want to continue? (yes/no) y [ INFO ] Stage: Environment setup Configuration files: ['/etc/ovirt-host-deploy.conf.d/50-fakevmstats.conf', '/etc/ovirt-host-deploy.conf.d/50-faqemu.conf', '/etc/ovirt-host-deploy.conf.d/50-offline-packager.conf'] Log file: /tmp/ovirt-host-deploy-20170509143602-zo5v24.log Version: otopi-1.7.0_master () Version: ovirt-host-deploy-1.7.0_master () [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment customization [ INFO ] Kdump unsupported [ INFO ] Stage: Setup validation [WARNING] Cannot validate host name settings, reason: resolved host does not match any of the local addresses [WARNING] Grubby not present - not setting kernel arguments. [ ERROR ] Failed to execute stage 'Setup validation': 'VIRT/enable' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination Looking at the log file showed the following errors: 2017-05-09 14:36:02,309+0300 DEBUG otopi.context context._executeMethod:128 Stage boot METHOD otopi.plugins.otopi.packagers.yumpackager.Plugin._boot 2017-05-09 14:36:02,316+0300 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpackager._boot:184 Cannot initialize miniyum Traceback (most recent call last): File "/home/herabus/otopi/src/bin/../plugins/otopi/packagers/yumpackager.py", line 176, in _boot self._refreshMiniyum() File "/home/herabus/otopi/src/bin/../plugins/otopi/packagers/yumpackager.py", line 134, in _refreshMiniyum constants.PackEnv.YUM_ENABLED_PLUGINS File "/home/herabus/otopi/src/bin/../plugins/otopi/packagers/yumpackager.py", line 61, in _getMiniYum from otopi import miniyum File "/home/herabus/otopi/src/otopi/miniyum.py", line 17, in <module> import rpmUtils.miscutils ImportError: No module named rpmUtils.miscutils 2017-05-09 14:36:04,550+0300 DEBUG otopi.plugins.otopi.network.hostname plugin.execute:921 execute-output: ('/bin/ip', 'addr', 'show') stdout: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 4c:72:b9:6c:e5:f9 brd ff:ff:ff:ff:ff:ff 3: wlp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether ba:4a:1b:2f:98:ca brd ff:ff:ff:ff:ff:ff 4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:61:40:ef:1d brd ff:ff:ff:ff:ff:ff inet 172.17.0.1/16 scope global docker0 valid_lft forever preferred_lft forever 2017-05-09 14:36:04,550+0300 DEBUG otopi.plugins.otopi.network.hostname plugin.execute:926 execute-output: ('/bin/ip', 'addr', 'show') stderr: 2017-05-09 14:36:04,551+0300 DEBUG otopi.plugins.otopi.network.hostname hostname._validation:100 my addresses: ['127.0.1.1', '127.0.1.1', '127.0.1.1'] 2017-05-09 14:36:04,551+0300 DEBUG otopi.plugins.otopi.network.hostname hostname._validation:101 local addresses: [u'172.17.0.1'] 2017-05-09 14:36:04,552+0300 WARNING otopi.plugins.otopi.network.hostname hostname._validation:106 Cannot validate host name settings, reason: resolved host does not match any of the local addresses Traceback (most recent call last): File "/home/herabus/otopi/src/otopi/context.py", line 132, in _executeMethod method['method']() File "/home/herabus/ovirt-host-deploy/src/bin/../plugins/ovirt-host-deploy/tune/tuned.py", line 75, in _validation if self.environment[odeploycons.VirtEnv.ENABLE]: KeyError: 'VIRT/enable' I tried starting the libvirtd service to see if that would make the VIRT/enable error go away or at least satisfy the requirements of ovirt-host-deploy, but it didn't seem to work. The other errors seem to be related to not having an IP address that ovirt-host-deploy can recognize. To package this for Debian, I would need to find the equivalent of yumpackager.py for aptitude/apt-get/apt, since it seems to be a dependency required by ovirt-host-deploy. TL;DR: How to enable the virt service and assign an IP address that ovirt-host-deploy can use. Write/Find a python script that is equivalent to yumpackager.py and miniyum.py so that that dependency for ovirt-host-deploy is satisfied as well. -- - Warm regards Leni Kadali Mutungi

On 5/15/17, Yedidyah Bar David <didi(a)redhat.com&gt; wrote: I'm guessing this means I can now move on to building ovirt-engine. This is very useful; will definitely try this out. Thanks. I wouldn't have come this far without the community's help and the documentation. Okay. Will try to look into this as well. Alright. Good to know. :) Well, my aim is to run oVirt *on* Debian, similar to how it is run and used by users on say Fedora or RHEL/CentOS. So that's what is guiding me. If your suggestions need to revised in the light of that, do let me know. - Warm regards Leni Kadali Mutungi

On Tue, May 16, 2017 at 9:51 AM, Yedidyah Bar David <didi(a)redhat.com&gt; wrote: I now see (as I expected) that Debian has a similar policy: https://wiki.debian.org/Java/MavenRepoSpec Of course, you can still try to mostly follow the current rpm/maven packaging, and have eventually something working. But Debian will not accept it. To make Debian do accept it, you'll probably need to "solve" the above bug first, for Debian. But perhaps Debian has better tools for that than Fedora, so it might require less work :-) -- Didi

On 05/19/2017 05:38 AM, Leni Kadali Mutungi wrote: Currently the oVirt engine has its own mechanism to start the application server, you don't need to (and should not) start it yourself with the 'standalone.sh' script. All you need to do is to tell the engine where the application server is installed. To do so you need to set the 'JBOSS_HOME' home in the engine configuration. The easiest way to do that is to add the '--jboss-home' option to the 'engine-setup' command: engine-setup --jboss-home=<JBOSS_HOME> That will add the following to the generated 'engine.conf.d/10-setup-jboss.conf' file: JBOSS_HOME="<JBOSS_HOME>" You can also change that file manually, if you move the application server to a different directory, for example.