[Engine-devel] [QE] oVirt 3.3.2 RC status
by Sandro Bonazzola
Hi,
we've scheduled oVirt 3.3.2 RC build on 2013-12-11 [1]
A bug tracker is available at [2] and it shows only 4 bugs still blocking the release:
Whiteboard Bug ID Summary
integration 1036209 [AIO] ssh issues
storage 1022961 Running a VM from a gluster domain uses mount instead of gluster URI
virt 1029885 cloud-init testcase does not work in engine 3.3.1
virt 1025829 sysprep floppy is not attached to Windows 2008 R2 machine - even when specifically checked in Run Once
Please provide an ETA for the above bugs.
1036209 [AIO] ssh issues: patch merged on master branch, ready to be merged (hopefully today) on 3.3 and 3.3.2 branches.
For those who want to help testing the bugs, I suggest to add yourself as QA contact for the bug and add yourself to the testing page [3].
Thanks to all which have already started testing beta release!
Maintainers should fill release notes before RC build, the page has been created here [4]
[1] http://www.ovirt.org/OVirt_3.3.z_release-management
[2] https://bugzilla.redhat.com/1027349
[3] http://www.ovirt.org/Testing/Ovirt_3.3.2_testing
[4] http://www.ovirt.org/OVirt_3.3.2_release_notes
Thanks,
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
11 years
[Engine-devel] Setting cluster CPU
by Sandro Bonazzola
Hi,
I'm trying to set the cluster CPU type while adding the first host to the Default cluster.
I know how to set the CPU type on a new cluster, since I'll do that in AIO plugin.
But I'm not sure to understand how to set the CPU on an existing cluster.
Should it be enough to specify cpu arg while adding the host to the cluster?
(before adding an host, cpu is None on the cluster)
Because I'm trying to do that without success (obtaining a sandybridge cluster while specifying westmere cpu).
Michael, can you take a look at http://gerrit.ovirt.org/22129 and advise?
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
11 years
[Engine-devel] Problems debugging client code
by Eli Mesika
Hi
Debugging client code I got this when trying to connect from Google Chrom :
********************************************************
Oops! Google Chrome could not connect to 127.0.0.1:8080
Try reloading the page
********************************************************
any ideas ???
I am following instructions from README.developer and using f19 with google-chrome-stable-31.0.1650.63-1.x86_64
Thanks
Eli
11 years
[Engine-devel] [Bug] Small Typo in api.xsd
by Sven Kieske
Hi,
I just was reading through the new cloud-init api integration and found
a small typo in:
backend/manager/modules/restapi/interface/definition/src/main/resources/api.xsd
Line 606:
It is: " <!-- Extrenal tasks -->" but should be
" <!-- External tasks -->", I guess.
--
Mit freundlichen Grüßen / Regards
Sven Kieske
Systemadministrator
Mittwald CM Service GmbH & Co. KG
Königsberger Straße 6
32339 Espelkamp
T: +49-5772-293-100
F: +49-5772-293-333
https://www.mittwald.de
Geschäftsführer: Robert Meyer
St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
11 years
[Engine-devel] make is failing in ovirt-engine master
by Kanagaraj
Hi,
make clean install-dev PREFIX="$HOME/ovirt-engine" is failing with
following error on master branch.
if [ "1" != 0 ]; then \
build/python-check.sh; \
fi
packaging/setup/ovirt_engine_setup/database.py:365:80: E501 line too
long (82 > 79 characters)
make[1]: *** [python-validation] Error 1
make[1]: Leaving directory `/home/kanagaraj/workspace/ovirt-engine'
make: *** [all-dev] Error 2
Can someone please fix this?
Thanks,
Kanagaraj
11 years
[Engine-devel] master is broken by Common#VdcActionUtilsTest ??
by Michael Pasternak
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:testCompile (default-testCompile) on project common: Compilation failure: Compilation
failure:
[ERROR] /home/mpastern/Coding/ovirt/ovirt-engine/backend/manager/modules/common/src/test/java/org/ovirt/engine/core/common/VdcActionUtilsTest.java:[13,42] error: package
org.ovirt.engine.core.common.action does not exist
[ERROR] /home/mpastern/Coding/ovirt/ovirt-engine/backend/manager/modules/common/src/test/java/org/ovirt/engine/core/common/VdcActionUtilsTest.java:[14,52] error: cannot
find symbol
[ERROR] package org.ovirt.engine.core.common.businessentities
[ERROR] /home/mpastern/Coding/ovirt/ovirt-engine/backend/manager/modules/common/src/test/java/org/ovirt/engine/core/common/VdcActionUtilsTest.java:[15,52] error: cannot
find symbol
[ERROR] package org.ovirt.engine.core.common.businessentities
[ERROR] /home/mpastern/Coding/ovirt/ovirt-engine/backend/manager/modules/common/src/test/java/org/ovirt/engine/core/common/VdcActionUtilsTest.java:[16,52] error: cannot
find symbol
[ERROR] package org.ovirt.engine.core.common.businessentities
[ERROR] /home/mpastern/Coding/ovirt/ovirt-engine/backend/manager/modules/common/src/test/java/org/ovirt/engine/core/common/VdcActionUtilsTest.java:[17,52] error: cannot
find symbol
[ERROR] package org.ovirt.engine.core.common.businessentities
[ERROR] /home/mpastern/Coding/ovirt/ovirt-engine/backend/manager/modules/common/src/test/java/org/ovirt/engine/core/common/VdcActionUtilsTest.java:[18,52] error: cannot
find symbol
[ERROR] package org.ovirt.engine.core.common.businessentities
[ERROR] /home/mpastern/Coding/ovirt/ovirt-engine/backend/manager/modules/common/src/test/java/org/ovirt/engine/core/common/VdcActionUtilsTest.java:[19,52] error: cannot
find symbol
[ERROR] package org.ovirt.engine.core.common.businessentities
[ERROR] /home/mpastern/Coding/ovirt/ovirt-engine/backend/manager/modules/common/src/test/java/org/ovirt/engine/core/common/VdcActionUtilsTest.java:[20,52] error: cannot
find symbol
[ERROR] package org.ovirt.engine.core.common.businessentities
[ERROR] /home/mpastern/Coding/ovirt/ovirt-engine/backend/manager/modules/common/src/test/java/org/ovirt/engine/core/common/VdcActionUtilsTest.java:[21,52] error: cannot
find symbol
...
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:testCompile (default-testCompile) on
project common: Compilation failure
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:414)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:357)
Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure
at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:656)
at org.apache.maven.plugin.TestCompilerMojo.execute(TestCompilerMojo.java:161)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
--
Michael Pasternak
RedHat, ENG-Virtualization R&D
11 years
[Engine-devel] Fwd: [Users] oVirt Cloud-Init integration REST-API
by Sven Kieske
Hi,
I think this may be the more appropriate list to discuss this issue?
I fear this isn't integrated yet and can't be integrated in 3.3.1 or 3.3.2?
-------- Original-Nachricht --------
Betreff: [Users] oVirt Cloud-Init integration REST-API
Datum: Fri, 6 Dec 2013 10:25:42 +0000
Von: Sven Kieske <S.Kieske(a)mittwald.de>
An: gpadgett(a)redhat.com <gpadgett(a)redhat.com>, users(a)ovirt.org
<users(a)ovirt.org>
Hi,
we want to utilize Cloud-Init via REST-API, like mentioned on
the feature page in the wiki:
http://www.ovirt.org/Features/Cloud-Init_Integration
but looking at api?rsdl I do not find any clue
if this is implemented already in 3.3.1?
if yes, how to call this function?
if no, can we hack something in the db to activate it
or at least use the function to automatic build the
cd-roms which get passed to the vms?
I really need this feature.
Thanks for your help.
--
Mit freundlichen Grüßen / Regards
Sven Kieske
Systemadministrator
Mittwald CM Service GmbH & Co. KG
Königsberger Straße 6
32339 Espelkamp
T: +49-5772-293-100
F: +49-5772-293-333
https://www.mittwald.de
Geschäftsführer: Robert Meyer
St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
11 years
[Engine-devel] restapi: Permissions in Capabilities (#859225)
by Ori Liel
When listing the application's capabilities we currently show 'permissions' both for each version, and outside versions altogether:
GET .../api/capabilities
<capabilities>
<permits></permits>
<version major="3" minor="1" href="/api/capabilities/332e3133-2e31-332e-3133-2e31332e3133" id="332e3133-2e31-332e-3133-2e31332e3133">
<permits>...</permits>
</version>
<version major="3" minor="0" href="/api/capabilities/332e3033-2e30-332e-3033-2e30332e3033" id="332e3033-2e30-332e-3033-2e30332e3033">
<permits>...</permits>
</version>
</capabilities>
1) Permissions should only exist within a version; their current existence outside 'version' is for backwards compatibility only. We assume that no one (except perhaps Automation) uses these non-version-specific permissions these days, and we'd like to remove them.
2) Regarding permissions within a version - Oded brought up that some permissions which are only relevant for 3.1 are listed also under 3.0 (for example, quota related permissions). In order for the API layer to be able to group permissions by version, permission<-->version metadata must exist somewhere. The permissions enum in the engine seems a natural place to put it, as Michael commented. Setting out to do this, I realized that which-permission-belongs-to-which-version is knowledge that I don't have, and don't really know how to get efficiently, and I sort of got stuck because of this. Ideas regarding this issue?
Thanks,
Ori.
11 years
Re: [Engine-devel] Jenkins JAVA_HOME
by Itamar Heim
On 12/05/2013 09:55 PM, Gustavo Frederico Temple Pedrosa wrote:
> Hello all,
>
> I have two changes that the build failed with "Error: JAVA_HOME is not
> defined correctly."
>
> Anyone knows how I fix this?
more details/link?
11 years
