[ovirt-users] [kolla] Looking for Docker images for Cinder, Glance etc for oVirt
Hello all. I am trying to use the Cinder and Glance Docker images you provide in relation to the setup here: http://www.ovirt.org/develop/release-management/features/cinderglance-docker-integration/ I tried to run `sudo docker pull kollaglue/centos-rdo-glance-registry:latest` and got an error of not found. I thought that it could possible to use a Dockerfile to spin up an equivalent of it, so I would like some guidance on how to go about doing that. Best practices and so on. Alternatively, if it is possible, may you point me in the direction of the equivalent images mentioned in the guides if they have been superseded by something else? Thanks. CCing the oVirt users and devel lists to see if anyone has experienced something similar. -- - Warm regards Leni Kadali Mutungi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Building oVirt engine on Debian
> On Thu, Jun 8, 2017 at 6:28 AM, Leni Kadali Mutungi > <lenikmutu...@gmail.com> wrote: >> I assigned the CentOS VM 3GB of RAM, so that could very well be the >> problem. So the next step will be to increase the RAM of the VM to 4GB >> and report back with my findings. Results of the build. It managed to move on from the point where it freezed. Here's the output: [INFO] weaveinfo Join point 'constructor-execution(void com.google.gwt.dev.jjs.impl.ControlFlowAnalyzer.(com.google.gwt.dev.jjs.ast.JProgram))' in Type 'com.google.gwt.dev.jjs.impl.ControlFlowAnalyzer' (ControlFlowAnalyzer.java:905) advised by after advice from 'org.ovirt.engine.ui.gwtaop.DontPrune' (DontPrune.java) [INFO]Compile of permutations succeeded [INFO]Compilation succeeded -- 357.776s [INFO] Linking into /home/centos/git/ovirt-engine/frontend/webadmin/modules/userportal-gwtp/target/generated-gwt/userportal [INFO]Link succeeded [INFO]Linking succeeded -- 1.889s [INFO] [INFO] --- maven-war-plugin:2.2:war (default-war) @ userportal --- [INFO] Packaging webapp [INFO] Assembling webapp [userportal] in [/home/centos/git/ovirt-engine/frontend/webadmin/modules/userportal-gwtp/target/userportal-4.2.0-SNAPSHOT] [INFO] Processing war project [INFO] Copying webapp webResources [/home/centos/git/ovirt-engine/frontend/webadmin/modules/userportal-gwtp/target/generated-gwt/userportal] to [/home/centos/git/ovirt-engine/frontend/webadmin/modules/userportal-gwtp/target/userportal-4.2.0-SNAPSHOT] [INFO] Copying webapp resources [/home/centos/git/ovirt-engine/frontend/webadmin/modules/userportal-gwtp/src/main/webapp] [INFO] Webapp assembled in [213 msecs] [INFO] Building war: /home/centos/git/ovirt-engine/frontend/webadmin/modules/userportal-gwtp/target/userportal-4.2.0-SNAPSHOT.war [INFO] WEB-INF/web.xml already added, skipping [INFO] [INFO] --- ovirt-jboss-modules-maven-plugin:2.0.1:attach-modules (default) @ userportal --- [INFO] The modules source directory "/home/centos/git/ovirt-engine/frontend/webadmin/modules/userportal-gwtp/src/main/modules" doesn't exist, no modules artifacts will be attached. [INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ userportal --- [INFO] Installing /home/centos/git/ovirt-engine/frontend/webadmin/modules/userportal-gwtp/target/userportal-4.2.0-SNAPSHOT.war to /home/centos/.m2/repository/org/ovirt/engine/ui/userportal/4.2.0-SNAPSHOT/userportal-4.2.0-SNAPSHOT.war [INFO] Installing /home/centos/git/ovirt-engine/frontend/webadmin/modules/userportal-gwtp/pom.xml to /home/centos/.m2/repository/org/ovirt/engine/ui/userportal/4.2.0-SNAPSHOT/userportal-4.2.0-SNAPSHOT.pom [INFO] [INFO] [INFO] Building frontend-symbols 4.2.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ frontend-symbols --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 2 resources [INFO] Copying 1 resource [INFO] Copying 1 resource [INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ frontend-symbols --- [INFO] No sources to compile [INFO] [INFO] --- maven-checkstyle-plugin:2.17:check (checkstyle) @ frontend-symbols --- [INFO] Starting audit... Audit done. [INFO] [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ frontend-symbols --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /home/centos/git/ovirt-engine/frontend/webadmin/modules/frontend-symbols/src/test/resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ frontend-symbols --- [INFO] No sources to compile [INFO] [INFO] --- maven-surefire-plugin:2.12.3:test (default-test) @ frontend-symbols --- [INFO] No tests to run. [INFO] [INFO] --- maven-jar-plugin:2.2:jar (default-jar) @ frontend-symbols --- [INFO] Building jar: /home/centos/git/ovirt-engine/frontend/webadmin/modules/frontend-symbols/target/frontend-symbols-4.2.0-SNAPSHOT.jar [INFO] [INFO] --- ovirt-jboss-modules-maven-plugin:2.0.1:attach-modules (default) @ frontend-symbols --- [INFO] The modules source directory "/home/centos/git/ovirt-engine/frontend/webadmin/modules/frontend-symbols/src/main/modules" doesn't exist, no modules artifacts will be attached. [INFO] [INFO] --- maven-jar-plugin:2.2:test-jar (test-jar) @ frontend-symbols --- [WARNING] JAR will be empty - no content was marked for inclusion! [INFO] Building jar: /home/centos/git/ovirt-engine/frontend/webadmin/modules/frontend-symbols/target/frontend-symbols-4.2.0-SNAPSHOT-tests.jar [INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ frontend-symbols --- [INFO] Installing /home/centos/git/ovirt-engine/frontend/webadmin/modules/frontend-symbols/target/frontend-symbols-
Re: [ovirt-users] Building oVirt engine on Debian
Results on trying a separate build on a CentOS VM are again a freeze at the same point as stated below: [INFO] weaveinfo Join point 'constructor-execution(void com.google.gwt.dev.jjs.impl.ControlFlowAnalyzer.(com.google.gwt.dev.jjs.ast.JProgram))' in Type 'com.google.gwt.dev.jjs.impl.ControlFlowAnalyzer' (ControlFlowAnalyzer.java:905) advised by after advice from 'org.ovirt.engine.ui.gwtaop.DontPrune' (DontPrune.java) I assigned the CentOS VM 3GB of RAM, so that could very well be the problem. So the next step will be to increase the RAM of the VM to 4GB and report back with my findings. I installed oVirt normally (from repos) on another CentOS VM and I noticed during engine-setup that the minimum amount of RAM is 4GB and the preferred amount is 16GB. I'm guessing 8GB is probably not enough to build oVirt, though I think it would do for a user install. -- - Warm regards Leni Kadali Mutungi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Building oVirt engine on Debian
On 6/6/17, Yedidyah Bar David <d...@redhat.com> wrote: > On Tue, Jun 6, 2017 at 6:55 AM, Leni Kadali Mutungi > <lenikmutu...@gmail.com> wrote: > So, did the engine also start successfully? Successfully ran `/home/user/ovirt_engine/share/ovirt-engine/services/ovirt-engine/ovirt-engine.py start` Unfortunately all I get is the home page. Trying to access the user portal and administration portal leaves me with a blank page. I guess this is the consequence of not building the GWT bits? -- - Warm regards Leni Kadali Mutungi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Building oVirt engine on Debian
Setup was successful. Attached is the message I received. I didn't mind the firewalld bits since I don't have that installed. However all the ovn-* commands didn't work. I tried locating their equivalents, thinking that they could be in the ovirt_engine folder or something along those lines. The `sed` and `keytool` commands worked. However I don't have OpenSwitch installed so I'll add that if it's necessary. -- - Warm regards Leni Kadali Mutungi ovirt_config Description: Binary data ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Building oVirt engine on Debian
On 6/1/17, Yedidyah Bar David <d...@redhat.com> wrote: > The message: > > No handlers could be found for logger > "ovirt.engine.ovirt_engine.configfile" > > is ugly, but harmless. It almost always appears in the setup log file. > You are welcome to open a bug about it, though. > > Not sure what's the problem with engine-setup. > > Can you please provide the full output? > > Does it create a log file? Can you check/share that one too? > Apologies I was unable to re-run the engine-setup. So here is the full output: herabus@trojan:~$ ovirt_engine/bin/engine-setup [ INFO ] Stage: Initializing Setup was run under unprivileged user this will produce development installation do you wish to proceed? (Yes, No) [No]: Yes [ INFO ] Stage: Environment setup Configuration files: [] Log file: /home/user/ovirt_engine/var/log/ovirt-engine/setup/ovirt-engine-setup-20170601195203-2d7fr3.log Version: otopi-1.7.0_master () [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment setup [ INFO ] Stage: Environment customization --== PRODUCT OPTIONS ==-- Configure Engine on this host (Yes, No) [Yes]: Yes Configure WebSocket Proxy on this host (Yes, No) [Yes]: Yes Configure VM Console Proxy on this host (Yes, No) [Yes]: Yes Install ovirt-provider-ovn(Yes, No) [Yes]?:Yes --== NETWORK CONFIGURATION ==-- Host fully qualified DNS name of this server [trojan.dragon.org]: 127.0.1.1 [ ERROR ] Host name is not valid: 127.0.1.1 is an IP address and not a FQDN. A FQDN is needed to be able to generate certificates correctly. Host fully qualified DNS name of this server [trojan.dragon.org]: trojan.dragon.org [ ERROR ] Host name is not valid: Command 'dig' is required but missing Host fully qualified DNS name of this server [trojan.dragon.org]: 127.0.1.1 [ ERROR ] Host name is not valid: 127.0.1.1 is an IP address and not a FQDN. A FQDN is needed to be able to generate certificates correctly. Host fully qualified DNS name of this server [trojan.dragon.org]: ^C[ ERROR ] Failed to execute stage 'Environment customization': SIG2 [ INFO ] Stage: Clean up Log file is located at /home/user/ovirt_engine/var/log/ovirt-engine/setup/ovirt-engine-setup-20170601195203-2d7fr3.log [ INFO ] Generating answer file '/home/user/ovirt_engine/var/lib/ovirt-engine/setup/answers/20170601195425-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed Attached is the log file. I hope that's alright. -- - Warm regards Leni Kadali Mutungi 20170601195425-setup.conf Description: Binary data ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Docker images for oVirt engine
On 5/22/17, Leni Kadali Mutungi <lenikmutu...@gmail.com> wrote: > Step 26/34 : RUN sed -i 's/multipathd.service //g' > /usr/lib/systemd/system/vdsmd.service > ---> Running in 67d580645333 > sed: can't read /usr/lib/systemd/system/vdsmd.service: No such file or > directory > The command '/bin/sh -c sed -i 's/multipathd.service //g' > /usr/lib/systemd/system/vdsmd.service' returned a non-zero code: 2 > Failed to build image 'ovirt/vdsc:master' > > Is vdsm a dependency for ovirt-containers? If so, how do I get the container > to successfully locate the service it seems to be looking for? It has occured to me that the error may be related to OpenShift and how I'm using it. Is OpenShift supposed to be a service that is running when building the oVirt container? How does it interact with the ovirt-containers? -- - Warm regards Leni Kadali Mutungi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Building oVirt engine on Debian
On 5/30/17, Leni Kadali Mutungi <lenikmutu...@gmail.com> wrote: > Managed to build successfully using a directory in home that the > non-root user can write to. However I when I ran the engine-setup, I > ran into the issue of specifying a fully qualified domain name. I > tried the possible answers I could think of (hostname.example.com, > 127.0.0.1) but they didn't seem to work. For this I searched the archives and the problem seems to be with what I've defined in my /etc/hosts file. So this one I know how to solve. So how do I get the engine-setup to run again? -- - Warm regards Leni Kadali Mutungi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Building oVirt engine on Debian
Managed to build successfully using a directory in home that the non-root user can write to. However I when I ran the engine-setup, I ran into the issue of specifying a fully qualified domain name. I tried the possible answers I could think of (hostname.example.com, 127.0.0.1) but they didn't seem to work. I then killed the process using Ctrl-C but I'm unable to re-run it again. The error I get is: No handlers could be found for logger "ovirt.engine.ovirt_engine.configfile" I tried running `locate` to find the code related to this but I was unable to find it. I have also run engine-cleanup but it didn't seem to work. engine-config didn't seem to give me the option of correcting my mistake. Advice on what to do next would be appreciated. -- - Warm regards Leni Kadali Mutungi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Building oVirt engine on Debian
I have read what is in the README.adoc and done all of it. Unfortunately, even with BUILD_ALL_USER_AGENTS=0, my computer would still freeze. I had to opt to not build the gwt ui instead. I hope it's not too important :P. Build went on fine. Ran into this issue: install: cannot create regular file '/usr/local/etc/logrotate.d/ovirt-engine-setup': Permission denied install: cannot create regular file '/usr/local/etc/logrotate.d/ovirt-engine-notifier': Permission denied install: cannot create regular file '/usr/local/etc/logrotate.d/ovirt-engine': Permission denied Makefile:301: recipe for target 'copy-recursive' failed make[2]: *** [copy-recursive] Error 1 make[2]: Leaving directory '/home/user/ovirt-engine' Makefile:420: recipe for target 'install-packaging-files' failed make[1]: *** [install-packaging-files] Error 2 make[1]: Leaving directory '/home/user/ovirt-engine' Makefile:521: recipe for target 'install-dev' failed make: *** [install-dev] Error 2 So usually I'd solve this by running as root, but since you've advised against it, what should I do to give the normal user permission to run this operation since the folder is owned by root and the group is staff? My looking through other responses to similar situations indicates to me that giving the non-root user access to this folder isn't recommended. What would be the best solution in my case? -- - Warm regards Leni Kadali Mutungi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Building oVirt engine on Debian
On 5/25/17, shubham dubey <sdubey...@gmail.com> wrote: > Hi, > I got the same problem once and it seems to be related to memory. > So first thing is make sure you have at least 4 gb of ram because thats the > minimum requirement for ovirt-engine to run. > If with 4gb+ ram you still getting error like this then you must have no > swap > memory turn on. In that case create a swap partition and turn on using > 'swapon /dev/swap-partition'. I have an existing swap partition. I turned swap off and on again, then attempted the build again. No luck. > If the error is still there then may be jvm is not able to access the > memory at > some place due to selinux. So disable the selinux then try again. Hmmm... I must say I'm not sure I use selinux. I use Debian; if I were using a RHEL-based distro, then I think this would be the case. -- - Warm regards Leni Kadali Mutungi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Building oVirt engine on Debian
On 5/25/17, Yedidyah Bar David <d...@redhat.com> wrote: > On Thu, May 25, 2017 at 6:05 AM, Leni Kadali Mutungi > <lenikmutu...@gmail.com> wrote: >> Ran `make clean install-dev` and the process freezes at: >> [INFO] weaveinfo Join point 'constructor-execution(void >> com.google.gwt.dev.jjs.impl.ControlFlowAnalyzer.(com.google.gwt.dev.jjs.ast.JProgram))' >> in Type 'com.google.gwt.dev.jjs.impl.ControlFlowAnalyzer' >> (ControlFlowAnalyzer.java:905) advised by after advice from >> 'org.ovirt.engine.ui.gwtaop.DontPrune' (DontPrune.java) >> >> My computer freezes at that point and I have to power it off. I tried >> doing it in the terminal without the Desktop Environment and I get the >> same result. The component being built is the UI Common Web. Advice on >> what to do next is appreciated. > > How long did you wait? 10-15 minutes. I tried 30 minutes at one point. > Perhaps you run out of memory? How much do you have? 8GB of RAM, 16GB of swap > Was the kernel not responding either? I have no idea; have never been in a situation where the kernel doesn't respond. When I was running the build in a virtual terminal, I would become unable to access the other terminals using Ctrl-Alt-F1 to F6 after I attempted to access the GUI on F7. > You can search the net for general debugging techniques for such > occasions. E.g. you can (beforehand): > echo 1 > /proc/sys/kernel/sysrq > Then you can press Alt-SysRq-m to see (in text console) memory status > and Alt-SysRq-t to see some information about each running task. I'll try this, thanks. > Did you increase number of max open file descriptors? No I didn't. Will also do. > Building the gwt ui is a very heavy process. > You can build for firefox only by passing BUILD_ALL_USER_AGENTS=0, > or not build it at all by passing BUILD_GWT=0. Will try this as a last resort. -- - Warm regards Leni Kadali Mutungi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Building oVirt engine on Debian
Ran `make clean install-dev` and the process freezes at: [INFO] weaveinfo Join point 'constructor-execution(void com.google.gwt.dev.jjs.impl.ControlFlowAnalyzer.(com.google.gwt.dev.jjs.ast.JProgram))' in Type 'com.google.gwt.dev.jjs.impl.ControlFlowAnalyzer' (ControlFlowAnalyzer.java:905) advised by after advice from 'org.ovirt.engine.ui.gwtaop.DontPrune' (DontPrune.java) My computer freezes at that point and I have to power it off. I tried doing it in the terminal without the Desktop Environment and I get the same result. The component being built is the UI Common Web. Advice on what to do next is appreciated. -- - Warm regards Leni Kadali Mutungi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Building ovirt-engine fails due to failing estCanReadFile(org.ovirt.engine.core.utils.servlet.ServletUtilsTest): We should not be able to read this file.
On 5/23/17, Yedidyah Bar David <d...@redhat.com> wrote: > On Tue, May 23, 2017 at 6:21 AM, Leni Kadali Mutungi > <lenikmutu...@gmail.com> wrote: >> Tried to build ovirt-engine on my computer using the command `make >> clean install-dev`, on Debian Testing. >> >> The full output of the error is as follows: >> https://paste.fedoraproject.org/paste/F6p~LVdNtFlpzQijMbSIYV5M1UNdIGYhyRLivL9gydE= > > Did you search the code for relevant parts of the error message? > Searching for 'We should not be able to read this file' finds it in > backend/manager/modules/utils/src/test/java/org/ovirt/engine/core/utils/servlet/ServletUtilsTest.java > twice - once when trying to read '/doesnotexist/iamprettysure', and > the other when trying to read '/etc/securetty'. I did not think to look for the file. Will remember this in future. > The latter file is 0600 on Fedora, RHEL and derivatives. I guess it's > readable for your user on your system, which might not be a good idea > in itself - but that's a different discussion. > > Some options for how to continue: > > 1. Submit a patch for the engine to change this test to test for some > other file that is more likely to be unreadable, e.g. /etc/shadow. > > 2. Locally set it on your system to be unreadable to you. > > 3. Assuming it's Debian's default, ask on Debian lists/forums to > change it to be non-world-readable and/or why it's not like that > already. > > 4. Ignore unit tests for now, 'make BUILD_UT=0 install-dev'. Check > README.adoc for details. I am ccing the Deb Virtualization Team for this, in the hopes that they may have a different opinion, but when I asked in the #debian IRC channel on OFTC, I was told that the file is now presently read by pam_securetty so permissions of 0600 would be fine, though the person responding didn't see the use of making the permissions stricter than they already are (0644). Maybe you could elaborate on the importance of having this set to 0600? Pending that I will go for option 4, and choose from options 1 to 3 when packaging for Debian. >> I modified the following variables in the Makefile to suit where the >> required files are: >> >> JS_DEPS_DIR=/home/user/ovirt-js-dependencies >> PYFLAKES=/usr/bin/pyflakes >> JBOSS_HOME=/home/user/wildfly-11.0.0.Alpha1 >> WILDFLY_OVERLAY_MODULES=/home/user/wildfly-11.0.0.Alpha1/modules >> >> I have pep8 but was unable to know how to correctly reference it in >> the Makefile, the syntax being: >> >> PEP8=pep8 > > This should probably be ok, unless your version of pep8 is too old/ > too new/has different defaults than what we use in CI (which is the > "common denominator"). > > Good luck, > >> >> Advice on this would be welcome. >> >> >> -- >> - Warm regards >> Leni Kadali Mutungi >> ___ >> Users mailing list >> Users@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users > > -- > Didi -- - Warm regards Leni Kadali Mutungi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Building ovirt-engine fails due to failing estCanReadFile(org.ovirt.engine.core.utils.servlet.ServletUtilsTest): We should not be able to read this file.
Tried to build ovirt-engine on my computer using the command `make clean install-dev`, on Debian Testing. The full output of the error is as follows: https://paste.fedoraproject.org/paste/F6p~LVdNtFlpzQijMbSIYV5M1UNdIGYhyRLivL9gydE= I modified the following variables in the Makefile to suit where the required files are: JS_DEPS_DIR=/home/user/ovirt-js-dependencies PYFLAKES=/usr/bin/pyflakes JBOSS_HOME=/home/user/wildfly-11.0.0.Alpha1 WILDFLY_OVERLAY_MODULES=/home/user/wildfly-11.0.0.Alpha1/modules I have pep8 but was unable to know how to correctly reference it in the Makefile, the syntax being: PEP8=pep8 Advice on this would be welcome. -- - Warm regards Leni Kadali Mutungi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Docker images for oVirt engine
On 5/22/17, Leni Kadali Mutungi <lenikmutu...@gmail.com> wrote: On 5/19/17, Juan Hernández <jhern...@redhat.com> wrote: > On 05/19/2017 05:20 AM, Leni Kadali Mutungi wrote: >> Running `make build` went fine until I saw this error: >> >> Step 26/34 : RUN sed -i 's/multipathd.service //g' >> /usr/lib/systemd/system/vdsmd.service >> ---> Running in 6a0948c94798 >> ERRO[0104] containerd: notify OOM events error=cgroup >> path for memory not found >> sed: can't read /usr/lib/systemd/system/vdsmd.service: No such file or >> directory >> The command '/bin/sh -c sed -i 's/multipathd.service //g' >> /usr/lib/systemd/system/vdsmd.service' returned a non-zero code: 2 >> Failed to build image 'ovirt/vdsc:master' >> >> I tried restarting the Docker daemon and re-running `make build`, >> since before this I got this error: >> >> Message from syslogd@localhost at May 19 06:07:57 ... kernel:[ >> 7498.623027] unregister_netdevice: waiting for lo to become free. >> Usage count = 1 >> > > Did that restart of the docker daemon resolve the problem? > > As far as I can tell that 'RUN sed' instruction that failed is correct. > I just re-checked it in my environment and it works correctly. Looks > more like a resources issue or a bug in docker itself. The message says > OOM, out of memory, is that machine low on memory maybe? > > Restart of the docker daemon does not solve the issue. Will try to see > how the memory issue can be solved, since I have enough memory (8GB), > so the problem is not hardware. Seems to be a problem related to the Debian Kernel. cgroup swap accounting is not enabled. I tried adding `cgroup_enable=memory swapaccount=1` to the GRUB_CMDLINE_LINUX_DEFAULT option in /etc/default/grub after the `quiet` option. After this I ran `sudo update-grub` and restarted my computer. The memory error has disappeared, the RUN sed instruction error has not. Step 26/34 : RUN sed -i 's/multipathd.service //g' /usr/lib/systemd/system/vdsmd.service ---> Running in 67d580645333 sed: can't read /usr/lib/systemd/system/vdsmd.service: No such file or directory The command '/bin/sh -c sed -i 's/multipathd.service //g' /usr/lib/systemd/system/vdsmd.service' returned a non-zero code: 2 Failed to build image 'ovirt/vdsc:master' Is vdsm a dependency for ovirt-containers? If so, how do I get the container to successfully locate the service it seems to be looking for? CCing Oved Ourfali since Juan Hernández is on vacation till May 29th. -- - Warm regards Leni Kadali Mutungi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Docker images for oVirt engine
On 5/19/17, Juan Hernández <jhern...@redhat.com> wrote: > Did that restart of the docker daemon resolve the problem? > > As far as I can tell that 'RUN sed' instruction that failed is correct. > I just re-checked it in my environment and it works correctly. Looks > more like a resources issue or a bug in docker itself. The message says > OOM, out of memory, is that machine low on memory maybe? Restart of the docker daemon does not solve the issue. Will try to see how the memory issue can be solved, since I have enough memory (8GB), so the problem is not hardware. -- - Warm regards Leni Kadali Mutungi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Building ovirt-host-deploy gives `configure: error: otopi-devtools required but missing`
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-Environment.md 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. /bin/standalone.sh (Unix / Linux) -- - Warm regards Leni Kadali Mutungi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Docker images for oVirt engine
Running `make build` went fine until I saw this error: Step 26/34 : RUN sed -i 's/multipathd.service //g' /usr/lib/systemd/system/vdsmd.service ---> Running in 6a0948c94798 ERRO[0104] containerd: notify OOM events error=cgroup path for memory not found sed: can't read /usr/lib/systemd/system/vdsmd.service: No such file or directory The command '/bin/sh -c sed -i 's/multipathd.service //g' /usr/lib/systemd/system/vdsmd.service' returned a non-zero code: 2 Failed to build image 'ovirt/vdsc:master' I tried restarting the Docker daemon and re-running `make build`, since before this I got this error: Message from syslogd@localhost at May 19 06:07:57 ... kernel:[ 7498.623027] unregister_netdevice: waiting for lo to become free. Usage count = 1 -- - Warm regards Leni Kadali Mutungi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Docker images for oVirt engine
On 5/15/17, Juan Hernández <jhern...@redhat.com> wrote:
> The tool that builds and deploy the containers to the OpenShift cluster
> is a program written in Go. It is compiled when you run 'make ...'. That
> means that you need to have the go development environment installed.
> For example, in CentOS or Fedora:
>
> yum -y install golang
>
> Once you have it installed, try again 'make build' and 'make deploy'.
>
> I'll try to update the documentation to explain that.
Installed Go. For some reason, building still refuses to work.
user@localhost:~/ovirt-containers$ sudo make build
for godep in gopkg.in/ini.v1 ; do \
GOPATH=""/tools"" go get ${godep}; \
done
GOPATH=""/tools"" go install ovirt/cmd/build
can't load package: package ovirt/cmd/build: cannot find package
"ovirt/cmd/build" in any of:
/usr/lib/go-1.7/src/ovirt/cmd/build (from $GOROOT)
/tools/src/ovirt/cmd/build (from $GOPATH)
Makefile:40: recipe for target 'tools/bin/build' failed
make: *** [tools/bin/build] Error 1
I looked at the tools/src/ovirt/cmd/build directory and it had the
build.go file. I don't have the ovirt subdirectory in the
/usr/lib/go-1.7/src/ directory. Any ideas on how to get it there?
--
- Warm regards
Leni Kadali Mutungi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Building ovirt-host-deploy gives `configure: error: otopi-devtools required but missing`
On 5/15/17, Yedidyah Bar David <d...@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. > This is very useful; will definitely try this out. > Anyway, congrats for a nice progress! Thanks. I wouldn't have come this far without the community's help and 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:RECEIVEenv-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:RECEIVEVALUE 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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Fwd: [Pkg-libvirt-discuss] Packaging oVirt for Debian
Forwarding this so that it is seen on oVirt's mailing list as well. In future, I'll try to make sure that I mail both the Debian Virtualization team and the oVirt users insofar as the topic is relevant to both sides. -- Forwarded message -- From: Guido Günther <a...@sigxcpu.org> Date: Mon, 15 May 2017 08:13:52 +0200 Subject: Re: [Pkg-libvirt-discuss] Packaging oVirt for Debian To: Leni Kadali Mutungi <lenikmutu...@gmail.com> On Mon, May 15, 2017 at 05:20:19AM +0300, Leni Kadali Mutungi wrote: > Hello all. This is where I am so far with the compiling and packaging. > > http://lists.ovirt.org/pipermail/users/2017-April/081523.html Nice you're making progress! > > I am now looking for how to enable the virt service and assign an IP > address that > ovirt-host-deploy can use. > > Also it seems that the yumpackager.py and miniyum.py scripts are > dependencies for ovirt-host-deploy. So it seems I need to 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, because setting it to not use a package was a short-term > solution to get it to run successfully. Have a look at python-apt. That will allow you to write a wrapper similar to miniyum.py. > > So if I could be pointed in the direction of a suitable script that > would work with Debian's aptitude, apt-get and apt in a similar > manner, I'd be much obliged. Please keep them mailing list in cc: so more people get a chance to help you! Cheers, -- Guido -- - Warm regards Leni Kadali Mutungi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Docker images for oVirt engine
Managed to run the OpenShift cluster well enough. When I went into the
ovirt-containers directory and tried to run `make build`, I got the
following error:
for godep in gopkg.in/ini.v1 ; do \
GOPATH=""/home/herabus/ovirt-containers/tools"" go get ${godep}; \
done
/bin/sh: 2: go: Permission denied
Makefile:40: recipe for target 'tools/bin/build' failed
make: *** [tools/bin/build] Error 127
So I ran `sudo make build` instead and got the following error:
for godep in gopkg.in/ini.v1 ; do \
GOPATH=""/tools"" go get ${godep}; \
done
/bin/sh: 2: go: not found
Makefile:40: recipe for target 'tools/bin/build' failed
make: *** [tools/bin/build] Error 127
Running `sudo make deploy` gave me this error:
for godep in gopkg.in/ini.v1 ; do \
GOPATH=""/tools"" go get ${godep}; \
done
/bin/sh: 2: go: not found
Makefile:40: recipe for target 'tools/bin/deploy' failed
make: *** [tools/bin/deploy] Error 127
--
- Warm regards
Leni Kadali Mutungi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Docker images for oVirt engine
> On 5/10/17, Barak Korren <bkor...@redhat.com> wrote: >> That one is obsolete AFAIK. The oVirt container images are now being >> worked on in the 'ovirt-containers' repo. Checked it out. It seems more complicated than what I need, which would be just a Dockerfile that pulls the required image. The ovirt-containers repo seems to have a dependency on OpenCluster, which I think I won't need since I'm after a basic install on one machine for documentation purposes. Your advice is appreciated. -- - Warm regards Leni Kadali Mutungi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Docker images for oVirt engine
On 5/10/17, Barak Korren <bkor...@redhat.com> wrote: > That one is obsolete AFAIK. The oVirt container images are now being > worked on in the 'ovirt-containers' repo. > > GitHub generally contains a read-only mirror on the oVirt sources, > development work for most projects is done via gerrit.ovirt.org. > Thank you. Found it. -- - Warm regards Leni Kadali Mutungi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Docker images for oVirt engine
I noticed that there had been some discussion regarding Docker images in the devel mailing list. I wanted to confirm that this: https://github.com/oVirt/ovirt-container-engine is alright to use with Docker. If this isn't the official source to use, pointers in the right direction would appreciated. -- - Warm regards Leni Kadali Mutungi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Building ovirt-host-deploy gives `configure: error: otopi-devtools required but missing`
ts.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
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
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Building ovirt-host-deploy gives `configure: error: otopi-devtools required but missing`
On 4/25/17, Douglas Landgraf <dland...@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/90D0k1AyVPGDbNhk1WxlBl5M1UNdIGYhyRLivL9gydE= -- - Warm regards Leni Kadali Mutungi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] 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~o815M1UNdIGYhyRLivL9gydE= 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/90D0k1AyVPGDbNhk1WxlBl5M1UNdIGYhyRLivL9gydE= 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-Environment.md 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
Re: [ovirt-users] Compiling oVirt for Debian.
Also I noticed when running `make` and `make install` for otopi after
running ./configure with the --enable-java-sdk and --with-maven
options that in both instances, code (for lack of a better word) gets
downloaded from https://repo.maven.apache.org/. I was wondering if
there was a way instead to check if the latest jar and pom modules
have been downloaded and then continue with the build using what is
already there. For a user like myself who's on a capped connection,
that would helpful since it would trim the amount of data used. Of
course, it is possible that it is minimal, but I also thought it would
be handy to avoid the duplication of effort so to speak.
As an aside, at what time is the community online in IRC? I ask
because I have had difficulty working this out from the documentation
which says 07:00 UMT to 11:00 UMT (09:00 IST to 17:00 PST). I haven't
been able to work out what timezone UMT is (all I got was Universal
Military Time and a successor standard to GMT, which I was unable to
make sense of unfortunately) and all I got for IST was Indian Standard
Time which would be okay, only that PST stands for Pacific Standard
Time (PDT in the summer) and that wouldn't add up :)
However if the mailing list is the preferred option, then I shall be
more than happy to stick to that :D
On 4/21/17, Leni Kadali Mutungi <lenikmutu...@gmail.com> wrote:
> Have run into difficulties building ovirt-host-deploy. I tried to
> build otopi using the commands given in the INSTALL file and made sure
> to run `./configure` with the options --enable-java-sdk and
> --with-maven. Unfortunately, when I restarted the building of
> ovirt-host-deploy, I failed to make it past ./configure with the
> resulting error below:
>
> user@localhost:~/ovirt-host-deploy$ ./configure --enable-java-sdk
> --with-maven
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> checking whether make supports nested variables... yes
> checking for a sed that does not truncate output... /bin/sed
> checking whether NLS is requested... yes
> checking for msgfmt... /usr/bin/msgfmt
> checking for gmsgfmt... /usr/bin/msgfmt
> checking for xgettext... /usr/bin/xgettext
> checking for msgmerge... /usr/bin/msgmerge
> checking for a sed that does not truncate output... (cached) /bin/sed
> checking whether make sets $(MAKE)... (cached) yes
> checking whether ln -s works... yes
> checking if 'ln -sr' supported... yes
> checking for pyflakes... pyflakes
> checking for pep8... no
> checking for mvn... mvn
> checking for javac... javac
> checking for jar... jar
> checking for otopi-bundle... no
> checking for a Python interpreter with version >= 2.6... python
> checking for python... /usr/bin/python
> checking for python version... 2.7
> checking for python platform... linux2
> checking for python script directory...
> ${prefix}/lib/python2.7/dist-packages
> checking for python extension module directory...
> ${exec_prefix}/lib/python2.7/dist-packages
> checking python module: otopi... yes
> configure: error: otopi-devtools required but missing
>
> I've run ./configure with the options and without it, and I've got the
> same error. Sandro in IRC had suggested that I adapt the full options
> for ./configure in Fedora and use them in Debian. Those are as
> follows:
>
> ./configure --build=x86_64-redhat-linux-gnu
> --host=x86_64-redhat-linux-gnu --program-prefix=
> --disable-dependency-tracking --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 --info
> --docdir=/usr/share/doc/otopi-1.6.3 --disable-python-syntax-check
> --enable-java-sdk --with-local-version=otopi-1.6.3-0.0.master.fc26
> COMMONS_LOGGING_JAR=/usr/share/java/commons-logging.jar
> JUNIT_JAR=/usr/share/java/junit.jar
>
> I got stuck at `--build=x86_64-redhat-linux-gnu` since `uname -a`
> gives: Linux localhost 4.6.0-1-amd64 #1 SMP Debian 4.6.2-2
> (2016-06-25) x86_64 GNU/Linux
> I wasn't sure if I should substitute `x86_64-redhat-linux-gnu` with
> `x86_64-gnu-linux`. Also the ./configure script downloaded
> otopi-1.7.0.master so that I would need to change that as well as the
> reference to Fedora in
> `--with-local-version=otopi-1.6.3-0.0.master.fc26`. I went onto the
> #debian-next channel and was advised to spare myself future pain by
> looking into packaging the necessary stuff for Debian instead of
> trying to hack out a build that will be painful to maintai
Re: [ovirt-users] Compiling oVirt for Debian.
Have run into difficulties building ovirt-host-deploy. I tried to
build otopi using the commands given in the INSTALL file and made sure
to run `./configure` with the options --enable-java-sdk and
--with-maven. Unfortunately, when I restarted the building of
ovirt-host-deploy, I failed to make it past ./configure with the
resulting error below:
user@localhost:~/ovirt-host-deploy$ ./configure --enable-java-sdk --with-maven
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for a sed that does not truncate output... /bin/sed
checking whether NLS is requested... yes
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for a sed that does not truncate output... (cached) /bin/sed
checking whether make sets $(MAKE)... (cached) yes
checking whether ln -s works... yes
checking if 'ln -sr' supported... yes
checking for pyflakes... pyflakes
checking for pep8... no
checking for mvn... mvn
checking for javac... javac
checking for jar... jar
checking for otopi-bundle... no
checking for a Python interpreter with version >= 2.6... python
checking for python... /usr/bin/python
checking for python version... 2.7
checking for python platform... linux2
checking for python script directory... ${prefix}/lib/python2.7/dist-packages
checking for python extension module directory...
${exec_prefix}/lib/python2.7/dist-packages
checking python module: otopi... yes
configure: error: otopi-devtools required but missing
I've run ./configure with the options and without it, and I've got the
same error. Sandro in IRC had suggested that I adapt the full options
for ./configure in Fedora and use them in Debian. Those are as
follows:
./configure --build=x86_64-redhat-linux-gnu
--host=x86_64-redhat-linux-gnu --program-prefix=
--disable-dependency-tracking --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 --info
--docdir=/usr/share/doc/otopi-1.6.3 --disable-python-syntax-check
--enable-java-sdk --with-local-version=otopi-1.6.3-0.0.master.fc26
COMMONS_LOGGING_JAR=/usr/share/java/commons-logging.jar
JUNIT_JAR=/usr/share/java/junit.jar
I got stuck at `--build=x86_64-redhat-linux-gnu` since `uname -a`
gives: Linux localhost 4.6.0-1-amd64 #1 SMP Debian 4.6.2-2
(2016-06-25) x86_64 GNU/Linux
I wasn't sure if I should substitute `x86_64-redhat-linux-gnu` with
`x86_64-gnu-linux`. Also the ./configure script downloaded
otopi-1.7.0.master so that I would need to change that as well as the
reference to Fedora in
`--with-local-version=otopi-1.6.3-0.0.master.fc26`. I went onto the
#debian-next channel and was advised to spare myself future pain by
looking into packaging the necessary stuff for Debian instead of
trying to hack out a build that will be painful to maintain in future.
Pointers, docs, advice are all welcome.
On 4/20/17, Yedidyah Bar David <d...@redhat.com> wrote:
> On Thu, Apr 20, 2017 at 3:45 PM, Leni Kadali Mutungi
> <lenikmutu...@gmail.com> wrote:
>> On 4/18/17, Yedidyah Bar David <d...@redhat.com> wrote:
>>> On Sun, Apr 16, 2017 at 6:54 AM, Leni Kadali Mutungi
>>> <lenikmutu...@gmail.com> wrote:
>>>>>> I think that all of them are maintained on gerrit.ovirt.org, and most
>>>>>> have
>>>>>> mirrors on github.com/ovirt.
>>>>>>
>>>> Found all the source code on gerrit.ovirt.org; not all of it is
>>>> mirrored to github.com/ovirt
>>>>
>>>>>> If you haven't yet, you might want to check also:
>>>>>>
>>>>>> http://www.ovirt.org/develop/developer-guide/engine/engine-development-environment/
>>>>>> Adding to otopi support for apt/dpkg is indeed interesting and
>>>>>> useful,
>>>>>> but
>>>>>> imo isn't mandatory for a first milestone. Not having an apt packager
>>>>>> will
>>>>>> simply mean you can't install/update packages using otopi, but other
>>>>>> things
>>>>>> should work. Notably, you won't be able to use engine-setup for
>>>>>> upgrades,
>>>>>> at least not the way it's done with yum and versionlock.
>>>>
>>>> So does this mean I shouldn't bother with installing otopi, because
>>>> according to the development guide for
Re: [ovirt-users] Compiling oVirt for Debian.
On 4/18/17, Yedidyah Bar David <d...@redhat.com> wrote: > On Sun, Apr 16, 2017 at 6:54 AM, Leni Kadali Mutungi > <lenikmutu...@gmail.com> wrote: >>>> I think that all of them are maintained on gerrit.ovirt.org, and most >>>> have >>>> mirrors on github.com/ovirt. >>>> >> Found all the source code on gerrit.ovirt.org; not all of it is >> mirrored to github.com/ovirt >> >>>> If you haven't yet, you might want to check also: >>>> >>>> http://www.ovirt.org/develop/developer-guide/engine/engine-development-environment/ >>>> Adding to otopi support for apt/dpkg is indeed interesting and useful, >>>> but >>>> imo isn't mandatory for a first milestone. Not having an apt packager >>>> will >>>> simply mean you can't install/update packages using otopi, but other >>>> things >>>> should work. Notably, you won't be able to use engine-setup for >>>> upgrades, >>>> at least not the way it's done with yum and versionlock. >> >> So does this mean I shouldn't bother with installing otopi, because >> according to the development guide for RPM-based systems, it seems >> only the ovirt-host-deploy, ovirt-setup-lib, and ovirt-js-dependencies >> are the packages required. > > ovirt-host-deploy requires otopi, and also engine-setup (from the engine > git repo) does. So unless you want to start manually imitating what these > do (which might not be a terrible idea, if you want to understand more > deeply how things work, but will take more time), you do need otopi. > > Also please note that the above developer guide is probably not complete > or up-to-date - please check also README.adoc from the engine sources. > >> The guide for Debian is blank and marked as >> TODO. > > Indeed, patches are welcome :-) > > I expect at least some packages to be missing there, didn't check > personally. > >> Another query I had was that should I make the config files >> myself as referenced by the README or can I expect that it will be >> done during make install? > > which ones? postgresql's? It's automatically done when you install > from RPMs, but not in dev-env mode. So you'll have to do that > manually for now. I was referring to the configuration files referenced in the README docs for otopi, ovirt-host-deploy, ovirt-setup-lib, and ovirt-js-dependencies. I'm not sure that running the make install will put the required configuration files in the directories that the programs will expect to find them. If it turns out that that is the case, then I think I am all set. I installed postgresql from the Debian repositories. -- - Warm regards Leni Kadali Mutungi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Compiling oVirt for Debian.
>> I think that all of them are maintained on gerrit.ovirt.org, and most >> have >> mirrors on github.com/ovirt. >> Found all the source code on gerrit.ovirt.org; not all of it is mirrored to github.com/ovirt >> If you haven't yet, you might want to check also: >> >> http://www.ovirt.org/develop/developer-guide/engine/engine-development-environment/ >> Adding to otopi support for apt/dpkg is indeed interesting and useful, >> but >> imo isn't mandatory for a first milestone. Not having an apt packager >> will >> simply mean you can't install/update packages using otopi, but other >> things >> should work. Notably, you won't be able to use engine-setup for upgrades, >> at least not the way it's done with yum and versionlock. So does this mean I shouldn't bother with installing otopi, because according to the development guide for RPM-based systems, it seems only the ovirt-host-deploy, ovirt-setup-lib, and ovirt-js-dependencies are the packages required. The guide for Debian is blank and marked as TODO. Another query I had was that should I make the config files myself as referenced by the README or can I expect that it will be done during make install? -- - Warm regards Leni Kadali Mutungi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] How do you oVirt? Here the answers!
> > >> >> - Surprisingly we have someone running both engine and hypervisor on >> Ubuntu based system, within VMs. I'd like to hear more about this use case. >> >> I too would love to hear more about this use case. Sounds interesting. - Warm regards Leni Kadali Mutungi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Compiling oVirt for Debian.
Thank you both for the warm welcome. I had already gone through the development guide, but the other links are good; I will definitely check them out and get back to you. On 4/12/17, Yedidyah Bar David <d...@redhat.com> wrote: > On Wed, Apr 12, 2017 at 10:28 AM, Sandro Bonazzola <sbona...@redhat.com> > wrote: > >> Hi Leni, welcome to the oVirt community! >> >> On Wed, Apr 12, 2017 at 5:57 AM, Leni Kadali Mutungi < >> lenikmutu...@gmail.com> wrote: >> >>> Hello all. >>> >>> I am trying to install oVirt on Debian. So far I've managed to install >>> a good chunk of the dependencies. >> >> >> Nice to see interest in getting oVirt on Debian! I'm adding Milan Zamal >> who was looking into getting vdsm running on Debian. >> >> >> >>> However I haven't been able to >>> install otopi, ovirt-host-deploy, ovirt-js-dependencies, >>> ovirt-setup-lib since Debian has no packages for these. With the >>> exception of otopi (whose build instructions I was unable to make >>> sense of on GitHub), >>> everything else is to be gotten from Fedora/EPEL repos. >>> >> >> >> Please note that otopi is not supporting Debian yet. >> It's missing support for the packaging system used by Debian. It >> currently >> support only yum and dnf package managers. >> Being ovirt-host-deploy and ovirt-setup-lib depending on otopi, you'll >> need to work on otopi code first. >> > > Adding to otopi support for apt/dpkg is indeed interesting and useful, but > imo isn't mandatory for a first milestone. Not having an apt packager will > simply mean you can't install/update packages using otopi, but other things > should work. Notably, you won't be able to use engine-setup for upgrades, > at least not the way it's done with yum and versionlock. > > >> >> >>> >>> I had thought of using alien to convert from rpm to deb, but >>> apparently the recommended thing is to compile from source, since >>> using alien can lead to a complex version of dependency hell. >>> >>> I can download WildFly from source, though again the recommended >>> procedure is to install ovirt-engine-wildfly and >>> ovirt-wildfly-overlay. >>> >> >> I would suggest to get in touch with Wildfly community about having >> wildfly packaged for Debian. >> >> >>> >>> Any assistance in tracking down the source code of the above packages >>> so that I can install them is appreciated. >>> >> > I think that all of them are maintained on gerrit.ovirt.org, and most have > mirrors on github.com/ovirt. > > If you haven't yet, you might want to check also: > > http://www.ovirt.org/develop/developer-guide/engine/engine-development-environment/ > http://www.ovirt.org/develop/dev-process/working-with-gerrit/ > > The engine used to work on gentoo in the past, although I do not think > anyone tried that in the last 1.5 years, so the following is not up-to-date > or working, but can still give you some ideas: > > https://wiki.gentoo.org/wiki/OVirt > > Good luck and best regards, > > >> >>> -- >>> - Warm regards >>> Leni Kadali Mutungi >>> ___ >>> Users mailing list >>> Users@ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/users >>> >> >> >> >> -- >> >> SANDRO BONAZZOLA >> >> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R >> >> Red Hat EMEA <https://www.redhat.com/> >> <https://red.ht/sig> >> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> >> >> ___ >> Users mailing list >> Users@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >> >> > > > -- > Didi > -- - Warm regards Leni Kadali Mutungi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Compiling oVirt for Debian.
Hello all. I am trying to install oVirt on Debian. So far I've managed to install a good chunk of the dependencies. However I haven't been able to install otopi, ovirt-host-deploy, ovirt-js-dependencies, ovirt-setup-lib since Debian has no packages for these. With the exception of otopi (whose build instructions I was unable to make sense of on GitHub), everything else is to be gotten from Fedora/EPEL repos. I had thought of using alien to convert from rpm to deb, but apparently the recommended thing is to compile from source, since using alien can lead to a complex version of dependency hell. I can download WildFly from source, though again the recommended procedure is to install ovirt-engine-wildfly and ovirt-wildfly-overlay. Any assistance in tracking down the source code of the above packages so that I can install them is appreciated. -- - Warm regards Leni Kadali Mutungi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
