Building ovirt-host-deploy gives `configure: error: otopi-devtools required but missing`
Hello. I got the error mentioned in the subject when when trying to build ovirt-host-deploy. Full output here: https://paste.fedoraproject.org/paste/Dh7FF1XjhDa2TGNSBs~o815M1UNdIGYhyRLivL... The troubleshooting I've done so far is as follows: 1. Rebuilt otopi, running the commands `autoreconf -ivf` and then `./configure --enable-java-sdk --with-maven`. This made `make` download a host of stuff for otopi project from https://repo.maven.apache.org It did this again when I ran `make install`. When I went back to the ovirt-host-deploy directory, I ran `./configure`, both with the --enable-java-sdk and --with-maven options. Got the same error again. 2. I tried running entering the directory src/java and running `mvn install`. I received a build success message and then proceeded to run ./configure --build=x86_64-linux-gnu --host=x86_64-linux-gnu --program-prefix= --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/var/lib --mandir=/usr/share/man --disable-python-syntax-check --enable-java-sdk --with-local-version=otopi-1.7.0.master COMMONS_LOGGING_JAR=/usr/share/java/commons-logging.jar JUNIT_JAR=/usr/share/java/junit.jar I omitted the --disable-dependency-tracking and --docdir=/usr/share/doc/otopi-1.7.0 options because of the following error: configure: WARNING: unrecognized options: --disable-dependency-tracking and the fact that I didn't have the directory /usr/share/doc/otopi-1.7.0 respectively. I got the following output: https://paste.fedoraproject.org/paste/90D0k1AyVPGDbNhk1WxlBl5M1UNdIGYhyRLivL... Running `sudo make install` gives me the same errors. It seems otopi is failing to compile properly and as a result, running ./configure within the ovirt-host-deploy directory ends with an error saying otopi-devtools are missing. Documentation of my environment as it stands is here: https://github.com/leni1/oVirt-docs-Debian/blob/master/oVirt-Development-Env... Any ideas on what I should try next are welcome. -- - Warm regards Leni Kadali Mutungi
Hi Leni, On Tue, Apr 25, 2017 at 10:45 AM, Leni Kadali Mutungi <lenikmutungi@gmail.com> wrote:
Hello. I got the error mentioned in the subject when when trying to build ovirt-host-deploy. Full output here: https://paste.fedoraproject.org/paste/Dh7FF1XjhDa2TGNSBs~o815M1UNdIGYhyRLivL...
The troubleshooting I've done so far is as follows: 1. Rebuilt otopi, running the commands `autoreconf -ivf` and then `./configure --enable-java-sdk --with-maven`. This made `make` download a host of stuff for otopi project from https://repo.maven.apache.org It did this again when I ran `make install`. When I went back to the ovirt-host-deploy directory, I ran `./configure`, both with the --enable-java-sdk and --with-maven options. Got the same error again.
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. """
From configure --help:
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
2. I tried running entering the directory src/java and running `mvn install`. I received a build success message and then proceeded to run
./configure --build=x86_64-linux-gnu --host=x86_64-linux-gnu --program-prefix= --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/var/lib --mandir=/usr/share/man --disable-python-syntax-check --enable-java-sdk --with-local-version=otopi-1.7.0.master COMMONS_LOGGING_JAR=/usr/share/java/commons-logging.jar JUNIT_JAR=/usr/share/java/junit.jar
I omitted the --disable-dependency-tracking and --docdir=/usr/share/doc/otopi-1.7.0 options because of the following error: configure: WARNING: unrecognized options: --disable-dependency-tracking and the fact that I didn't have the directory /usr/share/doc/otopi-1.7.0 respectively. I got the following output: https://paste.fedoraproject.org/paste/90D0k1AyVPGDbNhk1WxlBl5M1UNdIGYhyRLivL...
Running `sudo make install` gives me the same errors. It seems otopi is failing to compile properly and as a result, running ./configure within the ovirt-host-deploy directory ends with an error saying otopi-devtools are missing. Documentation of my environment as it stands is here: https://github.com/leni1/oVirt-docs-Debian/blob/master/oVirt-Development-Env...
Any ideas on what I should try next are welcome.
-- - Warm regards Leni Kadali Mutungi _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Cheers Douglas
On 4/25/17, Douglas Landgraf <dlandgra@redhat.com> wrote:
Hi Leni,
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.
""" From configure --help:
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/
Will definitely try this out and send feedback. Thanks.
Fell free to share with us the output of make install.
Thanks Douglas
My apologies. I thought I had attached the output of `sudo make install`. Here it is: https://paste.fedoraproject.org/paste/90D0k1AyVPGDbNhk1WxlBl5M1UNdIGYhyRLivL... -- - Warm regards Leni Kadali Mutungi
On Tue, Apr 25, 2017 at 7:45 AM, Leni Kadali Mutungi <lenikmutungi@gmail.com> wrote:
Hello. I got the error mentioned in the subject when when trying to build ovirt-host-deploy. Full output here: https://paste.fedoraproject.org/paste/Dh7FF1XjhDa2TGNSBs~o815M1UNdIGYhyRLivL...
The troubleshooting I've done so far is as follows: 1. Rebuilt otopi, running the commands `autoreconf -ivf` and then `./configure --enable-java-sdk --with-maven`. This made `make` download a host of stuff for otopi project from https://repo.maven.apache.org It did this again when I ran `make install`. When I went back to the ovirt-host-deploy directory, I ran `./configure`, both with the --enable-java-sdk and --with-maven options. Got the same error again.
2. I tried running entering the directory src/java and running `mvn install`. I received a build success message and then proceeded to run
./configure --build=x86_64-linux-gnu --host=x86_64-linux-gnu --program-prefix= --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/var/lib --mandir=/usr/share/man --disable-python-syntax-check --enable-java-sdk --with-local-version=otopi-1.7.0.master COMMONS_LOGGING_JAR=/usr/share/java/commons-logging.jar JUNIT_JAR=/usr/share/java/junit.jar
I omitted the --disable-dependency-tracking and --docdir=/usr/share/doc/otopi-1.7.0 options because of the following error: configure: WARNING: unrecognized options: --disable-dependency-tracking and the fact that I didn't have the directory /usr/share/doc/otopi-1.7.0 respectively. I got the following output: https://paste.fedoraproject.org/paste/90D0k1AyVPGDbNhk1WxlBl5M1UNdIGYhyRLivL...
Running `sudo make install` gives me the same errors. It seems otopi is failing to compile properly and as a result, running ./configure within the ovirt-host-deploy directory ends with an error saying otopi-devtools are missing. Documentation of my environment as it stands is here: https://github.com/leni1/oVirt-docs-Debian/blob/master/oVirt-Development-Env...
Any ideas on what I should try next are welcome.
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
-- - Warm regards Leni Kadali Mutungi _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On 4/25/17, Jason Brooks <jbrooks@redhat.com> 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)
Hmmm... This sounds definitely worth trying.
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
Let me test it out on my own machine and see. -- - Warm regards Leni Kadali Mutungi
On Tue, Apr 25, 2017 at 10:27 PM, Leni Kadali Mutungi <lenikmutungi@gmail.com> wrote:
On 4/25/17, Jason Brooks <jbrooks@redhat.com> 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)
Hmmm... This sounds definitely worth trying.
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
Let me test it out on my own machine and see.
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,
-- - Warm regards Leni Kadali Mutungi _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Didi
On Wed, Apr 26, 2017 at 9:26 AM, Yedidyah Bar David <didi@redhat.com> wrote:
On Tue, Apr 25, 2017 at 10:27 PM, Leni Kadali Mutungi <lenikmutungi@gmail.com> wrote:
On 4/25/17, Jason Brooks <jbrooks@redhat.com> 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)
Hmmm... This sounds definitely worth trying.
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
Let me test it out on my own machine and see.
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.
Sorry. I now see that ovirt-host-deploy defaults to searching for otopi-bundle in a hard-coded path /usr/share/otopi. So if you want dev-env, passing same prefix will not be enough - you'll have to pass also --otopi-bundle=/path/to/otopi-bundle to ./configure . I admit I never heard about anyone using otopi in dev-env. IMO all the oVirt developers install otopi from rpm on their dev machines (me included). It should be quite easy to change the default to be $PREFIX/share/otopi if you want - I think it should not cause any new bugs. Patches are welcome :-)
If you want to package for debian, you should mostly use debian defaults for most things imo.
(This should still apply, as I think you'll package it on debian to use the same path as in rpm - /usr/share/otopi). Best,
Best,
-- - Warm regards Leni Kadali Mutungi _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Didi
-- Didi
# ./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
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",
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. 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 Wed, May 10, 2017 at 5:37 PM, Leni Kadali Mutungi <lenikmutungi@gmail.com> wrote:
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.
# ./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
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",
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. 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
You can ignore this warning for now and get to it later on.
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'
Now is the time to explain something. ovirt-host-deploy is not designed to be ran manually like you try. You will get the exact same error if you try to do this on CentOS or Fedora. The normal way it works is that the engine "bundles" it in a tarball, copies it to the target host using ssh, untars it there and runs it. It then talks with it - the engine sends some stuff, host-deploy replies, etc. The protocol they use is described in otopi, in the file README.dialog. otopi has (currently) two "dialects" - "human" (default) and "machine". The engine and ovirt-host-deploy talk using the machine dialog. To make ovirt-host-deploy talk with you using the machine dialog, you should run it with: ovirt-host-deploy DIALOG/dialect=str:machine To make it let you configure it, run it with: ovirt-host-deploy DIALOG/dialect=str:machine DIALOG/customization=bool:True To know what it expects at each stage, I suggest to have a look at an ovirt-host-deploy log generated on el7 or fedora. Anyway, congrats for a nice progress!
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.
If you check such a log file, you'll see there (among other things): DIALOG:SEND **%QStart: CUSTOMIZATION_COMMAND DIALOG:SEND ### DIALOG:SEND ### Customization phase, use 'install' to proceed DIALOG:SEND ### COMMAND> DIALOG:SEND **%QHidden: FALSE DIALOG:SEND ***Q:STRING CUSTOMIZATION_COMMAND DIALOG:SEND **%QEnd: CUSTOMIZATION_COMMAND DIALOG:RECEIVE env-query -k VIRT/enable DIALOG:SEND **%QStart: VIRT/enable DIALOG:SEND ### DIALOG:SEND ### Please specify value for 'VIRT/enable': DIALOG:SEND ### Response is VALUE VIRT/enable=type:value or ABORT VIRT/enable DIALOG:SEND ***Q:VALUE VIRT/enable DIALOG:SEND **%QEnd: VIRT/enable DIALOG:RECEIVE VALUE VIRT/enable=bool:true "SEND" is what the host-deploy sends, "RECEIVE" is what the engine replies. So host-deploy sent a prompt asking for a customization command, the engine sent the command 'env-query -k VIRT/enable', host-deploy then asked the engine to provide a value for 'VIRT/enable', and the engine replied 'VIRT/enable=bool:true'.
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.
As I said, you can ignore it for now. But IMO this isn't specific to Debian - search a bit and you'll find other similar cases.
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.
Last one will indeed be very interesting, but isn't mandatory for you to continue, if your stated goal is to have a Debian host managed by an oVirt engine. You can manually install all your stuff on the host, and use offlinepackager so that host-deploy will not try to install stuff for you. You'll then have a harder first-time-install, and will miss checking for updates etc. For these you'll indeed need to write something like debpackager, and probably minideb as well - engine-setup uses it directly, as otopi's packager isn't enough for it. I'd like to mention another point. As explained above, when the engine adds a host, it copies to it a bundle (tarfile). This bundle is not rpm/yum/dnf specific - it should work also on Debian. Normally, ovirt-host-deploy (the rpm package) is installed only on the engine machine. So if you do not care about the engine side for now, you should be able to try adding a Debian host to your engine already - just configure offline packager. This might be easier to debug then by manually running ovirt-host-deploy. Best, -- Didi
On 5/15/17, Yedidyah Bar David <didi@redhat.com> wrote:
Now is the time to explain something.
ovirt-host-deploy is not designed to be ran manually like you try.
You will get the exact same error if you try to do this on CentOS or Fedora.
The normal way it works is that the engine "bundles" it in a tarball, copies it to the target host using ssh, untars it there and runs it.
It then talks with it - the engine sends some stuff, host-deploy replies, etc.
I'm guessing this means I can now move on to building ovirt-engine.
The protocol they use is described in otopi, in the file README.dialog.
otopi has (currently) two "dialects" - "human" (default) and "machine". The engine and ovirt-host-deploy talk using the machine dialog.
To make ovirt-host-deploy talk with you using the machine dialog, you should run it with:
ovirt-host-deploy DIALOG/dialect=str:machine
To make it let you configure it, run it with:
ovirt-host-deploy DIALOG/dialect=str:machine DIALOG/customization=bool:True
To know what it expects at each stage, I suggest to have a look at an ovirt-host-deploy log generated on el7 or fedora.
Anyway, congrats for a nice progress! Thanks. I wouldn't have come this far without the community's help and
This is very useful; will definitely try this out. the documentation.
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.
If you check such a log file, you'll see there (among other things):
DIALOG:SEND **%QStart: CUSTOMIZATION_COMMAND DIALOG:SEND ### DIALOG:SEND ### Customization phase, use 'install' to proceed DIALOG:SEND ### COMMAND> DIALOG:SEND **%QHidden: FALSE DIALOG:SEND ***Q:STRING CUSTOMIZATION_COMMAND DIALOG:SEND **%QEnd: CUSTOMIZATION_COMMAND DIALOG:RECEIVE env-query -k VIRT/enable DIALOG:SEND **%QStart: VIRT/enable DIALOG:SEND ### DIALOG:SEND ### Please specify value for 'VIRT/enable': DIALOG:SEND ### Response is VALUE VIRT/enable=type:value or ABORT VIRT/enable DIALOG:SEND ***Q:VALUE VIRT/enable DIALOG:SEND **%QEnd: VIRT/enable DIALOG:RECEIVE VALUE VIRT/enable=bool:true
"SEND" is what the host-deploy sends, "RECEIVE" is what the engine replies.
So host-deploy sent a prompt asking for a customization command, the engine sent the command 'env-query -k VIRT/enable', host-deploy then asked the engine to provide a value for 'VIRT/enable', and the engine replied 'VIRT/enable=bool:true'.
Okay. Will try to look into this as well.
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.
As I said, you can ignore it for now. But IMO this isn't specific to Debian - search a bit and you'll find other similar cases. Alright. Good to know. :)
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.
Last one will indeed be very interesting, but isn't mandatory for you to continue, if your stated goal is to have a Debian host managed by an oVirt engine. You can manually install all your stuff on the host, and use offlinepackager so that host-deploy will not try to install stuff for you. You'll then have a harder first-time-install, and will miss checking for updates etc. For these you'll indeed need to write something like debpackager, and probably minideb as well - engine-setup uses it directly, as otopi's packager isn't enough for it.
I'd like to mention another point. As explained above, when the engine adds a host, it copies to it a bundle (tarfile). This bundle is not rpm/yum/dnf specific - it should work also on Debian. Normally, ovirt-host-deploy (the rpm package) is installed only on the engine machine. So if you do not care about the engine side for now, you should be able to try adding a Debian host to your engine already - just configure offline packager. This might be easier to debug then by manually running ovirt-host-deploy.
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 Mon, May 15, 2017 at 10:42 PM, Leni Kadali Mutungi <lenikmutungi@gmail.com> wrote:
On 5/15/17, Yedidyah Bar David <didi@redhat.com> wrote:
Now is the time to explain something.
ovirt-host-deploy is not designed to be ran manually like you try.
You will get the exact same error if you try to do this on CentOS or Fedora.
The normal way it works is that the engine "bundles" it in a tarball, copies it to the target host using ssh, untars it there and runs it.
It then talks with it - the engine sends some stuff, host-deploy replies, etc.
I'm guessing this means I can now move on to building ovirt-engine.
That would be great, but: 1. It will require a lot of work, mostly probably of packaging in Debian dependencies of the engine that are not yet there. 2. You'll be mostly walking the unwalked path. Most of the work on Debian support so far was on the hosts' side. Re (1.), you should also note that currently, the engine is not even packaged properly for Fedora/CentOS. I know this sounds weird, as everyone uses the packages we provide, but it's true - these packages are not compliant with Fedora's packaging guidelines. Why? Because we use maven for building the engine, and package also many dependencies simply as a result of maven getting them from maven central. See also: https://bugzilla.redhat.com/showdependencytree.cgi?id=1168605&hide_resolved=0 Best,
The protocol they use is described in otopi, in the file README.dialog.
otopi has (currently) two "dialects" - "human" (default) and "machine". The engine and ovirt-host-deploy talk using the machine dialog.
To make ovirt-host-deploy talk with you using the machine dialog, you should run it with:
ovirt-host-deploy DIALOG/dialect=str:machine
To make it let you configure it, run it with:
ovirt-host-deploy DIALOG/dialect=str:machine DIALOG/customization=bool:True
To know what it expects at each stage, I suggest to have a look at an ovirt-host-deploy log generated on el7 or fedora.
Anyway, congrats for a nice progress! Thanks. I wouldn't have come this far without the community's help and
This is very useful; will definitely try this out. the documentation.
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.
If you check such a log file, you'll see there (among other things):
DIALOG:SEND **%QStart: CUSTOMIZATION_COMMAND DIALOG:SEND ### DIALOG:SEND ### Customization phase, use 'install' to proceed DIALOG:SEND ### COMMAND> DIALOG:SEND **%QHidden: FALSE DIALOG:SEND ***Q:STRING CUSTOMIZATION_COMMAND DIALOG:SEND **%QEnd: CUSTOMIZATION_COMMAND DIALOG:RECEIVE env-query -k VIRT/enable DIALOG:SEND **%QStart: VIRT/enable DIALOG:SEND ### DIALOG:SEND ### Please specify value for 'VIRT/enable': DIALOG:SEND ### Response is VALUE VIRT/enable=type:value or ABORT VIRT/enable DIALOG:SEND ***Q:VALUE VIRT/enable DIALOG:SEND **%QEnd: VIRT/enable DIALOG:RECEIVE VALUE VIRT/enable=bool:true
"SEND" is what the host-deploy sends, "RECEIVE" is what the engine replies.
So host-deploy sent a prompt asking for a customization command, the engine sent the command 'env-query -k VIRT/enable', host-deploy then asked the engine to provide a value for 'VIRT/enable', and the engine replied 'VIRT/enable=bool:true'.
Okay. Will try to look into this as well.
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.
As I said, you can ignore it for now. But IMO this isn't specific to Debian - search a bit and you'll find other similar cases. Alright. Good to know. :)
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.
Last one will indeed be very interesting, but isn't mandatory for you to continue, if your stated goal is to have a Debian host managed by an oVirt engine. You can manually install all your stuff on the host, and use offlinepackager so that host-deploy will not try to install stuff for you. You'll then have a harder first-time-install, and will miss checking for updates etc. For these you'll indeed need to write something like debpackager, and probably minideb as well - engine-setup uses it directly, as otopi's packager isn't enough for it.
I'd like to mention another point. As explained above, when the engine adds a host, it copies to it a bundle (tarfile). This bundle is not rpm/yum/dnf specific - it should work also on Debian. Normally, ovirt-host-deploy (the rpm package) is installed only on the engine machine. So if you do not care about the engine side for now, you should be able to try adding a Debian host to your engine already - just configure offline packager. This might be easier to debug then by manually running ovirt-host-deploy.
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
-- Didi
On Tue, May 16, 2017 at 9:51 AM, Yedidyah Bar David <didi@redhat.com> wrote:
On Mon, May 15, 2017 at 10:42 PM, Leni Kadali Mutungi <lenikmutungi@gmail.com> wrote:
On 5/15/17, Yedidyah Bar David <didi@redhat.com> wrote:
Now is the time to explain something.
ovirt-host-deploy is not designed to be ran manually like you try.
You will get the exact same error if you try to do this on CentOS or Fedora.
The normal way it works is that the engine "bundles" it in a tarball, copies it to the target host using ssh, untars it there and runs it.
It then talks with it - the engine sends some stuff, host-deploy replies, etc.
I'm guessing this means I can now move on to building ovirt-engine.
That would be great, but:
1. It will require a lot of work, mostly probably of packaging in Debian dependencies of the engine that are not yet there.
2. You'll be mostly walking the unwalked path. Most of the work on Debian support so far was on the hosts' side.
Re (1.), you should also note that currently, the engine is not even packaged properly for Fedora/CentOS. I know this sounds weird, as everyone uses the packages we provide, but it's true - these packages are not compliant with Fedora's packaging guidelines. Why? Because we use maven for building the engine, and package also many dependencies simply as a result of maven getting them from maven central. See also:
https://bugzilla.redhat.com/showdependencytree.cgi?id=1168605&hide_resolved=0
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 :-)
Best,
The protocol they use is described in otopi, in the file README.dialog.
otopi has (currently) two "dialects" - "human" (default) and "machine". The engine and ovirt-host-deploy talk using the machine dialog.
To make ovirt-host-deploy talk with you using the machine dialog, you should run it with:
ovirt-host-deploy DIALOG/dialect=str:machine
To make it let you configure it, run it with:
ovirt-host-deploy DIALOG/dialect=str:machine DIALOG/customization=bool:True
To know what it expects at each stage, I suggest to have a look at an ovirt-host-deploy log generated on el7 or fedora.
Anyway, congrats for a nice progress! Thanks. I wouldn't have come this far without the community's help and
This is very useful; will definitely try this out. the documentation.
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.
If you check such a log file, you'll see there (among other things):
DIALOG:SEND **%QStart: CUSTOMIZATION_COMMAND DIALOG:SEND ### DIALOG:SEND ### Customization phase, use 'install' to proceed DIALOG:SEND ### COMMAND> DIALOG:SEND **%QHidden: FALSE DIALOG:SEND ***Q:STRING CUSTOMIZATION_COMMAND DIALOG:SEND **%QEnd: CUSTOMIZATION_COMMAND DIALOG:RECEIVE env-query -k VIRT/enable DIALOG:SEND **%QStart: VIRT/enable DIALOG:SEND ### DIALOG:SEND ### Please specify value for 'VIRT/enable': DIALOG:SEND ### Response is VALUE VIRT/enable=type:value or ABORT VIRT/enable DIALOG:SEND ***Q:VALUE VIRT/enable DIALOG:SEND **%QEnd: VIRT/enable DIALOG:RECEIVE VALUE VIRT/enable=bool:true
"SEND" is what the host-deploy sends, "RECEIVE" is what the engine replies.
So host-deploy sent a prompt asking for a customization command, the engine sent the command 'env-query -k VIRT/enable', host-deploy then asked the engine to provide a value for 'VIRT/enable', and the engine replied 'VIRT/enable=bool:true'.
Okay. Will try to look into this as well.
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.
As I said, you can ignore it for now. But IMO this isn't specific to Debian - search a bit and you'll find other similar cases. Alright. Good to know. :)
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.
Last one will indeed be very interesting, but isn't mandatory for you to continue, if your stated goal is to have a Debian host managed by an oVirt engine. You can manually install all your stuff on the host, and use offlinepackager so that host-deploy will not try to install stuff for you. You'll then have a harder first-time-install, and will miss checking for updates etc. For these you'll indeed need to write something like debpackager, and probably minideb as well - engine-setup uses it directly, as otopi's packager isn't enough for it.
I'd like to mention another point. As explained above, when the engine adds a host, it copies to it a bundle (tarfile). This bundle is not rpm/yum/dnf specific - it should work also on Debian. Normally, ovirt-host-deploy (the rpm package) is installed only on the engine machine. So if you do not care about the engine side for now, you should be able to try adding a Debian host to your engine already - just configure offline packager. This might be easier to debug then by manually running ovirt-host-deploy.
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
-- Didi
-- Didi
By the way, how does WildFly fit into all of this? Because I downloaded a zip file from their site as referenced here: https://github.com/leni1/oVirt-docs-Debian/blob/master/oVirt-Development-Env... and it seemed to me that zip contained a script that runs the WildFly server instance within the terminal. How is it supposed to interact with the oVirt engine and how do I make sure to run it such that there are no errors arising from not having it. As of now I run it as a standalone server according to the instructions in the README.txt file that comes with the zip file: Starting a Standalone Server ---------------------------- A WildFly standalone server runs a single instance. <JBOSS_HOME>/bin/standalone.sh (Unix / Linux) -- - Warm regards Leni Kadali Mutungi
On 05/19/2017 05:38 AM, Leni Kadali Mutungi wrote:
By the way, how does WildFly fit into all of this? Because I downloaded a zip file from their site as referenced here: https://github.com/leni1/oVirt-docs-Debian/blob/master/oVirt-Development-Env... and it seemed to me that zip contained a script that runs the WildFly server instance within the terminal. How is it supposed to interact with the oVirt engine and how do I make sure to run it such that there are no errors arising from not having it. As of now I run it as a standalone server according to the instructions in the README.txt file that comes with the zip file:
Starting a Standalone Server ---------------------------- A WildFly standalone server runs a single instance.
<JBOSS_HOME>/bin/standalone.sh (Unix / Linux)
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.
On 16 May 2017 at 09:51, Yedidyah Bar David <didi@redhat.com> wrote:
Re (1.), you should also note that currently, the engine is not even packaged properly for Fedora/CentOS. I know this sounds weird, as everyone uses the packages we provide, but it's true - these packages are not compliant with Fedora's packaging guidelines. Why? Because we use maven for building the engine, and package also many dependencies simply as a result of maven getting them from maven central. See also:
https://bugzilla.redhat.com/showdependencytree.cgi?id=1168605&hide_resolved=0
I guess we could walk the middle ground here for DEBs just like we do for RMPs no? Which means - have java dependency bundle packages and release from resources.ovirt.org... I would love to see a discussion on what it would take to get DEBs through the CI system. I guess we would need some sort of 'build-artifacts.sh.deb' (Or deb8? dep9? not sure what is the convention for Debian version shorthands), some Debian build slaves and Debian equivalents of mock_runner.sh and repoan. -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
participants (6)
-
Barak Korren -
Douglas Landgraf -
Jason Brooks -
Juan Hernández -
Leni Kadali Mutungi -
Yedidyah Bar David