Re: [Engine-devel] Fwd: [Users] oVirt Cloud-Init integration REST-API
Hi, I appreciate your backport! Are the RPMs in the beta repo also updated? I would test this feature intensive, so you might get valuable feedback. -- 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 ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] [QE] oVirt 3.3.2 RC status
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 3 bugs still blocking the release: Whiteboard Bug ID Summary storage 1022961 Running a VM from a gluster domain uses mount instead of gluster URI virt1029885 cloud-init testcase does not work in engine 3.3.1 virt1025829 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. oVirt 3.3.2 beta testing is in progress, thanks to all who already started testing it! For those willing to help testing the bugs, I suggest to add yourself as QA contact for the bug and add yourself to the testing page [3]. 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 ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] [QE] oVirt 3.3.2 RC status
- Original Message - From: Sandro Bonazzola sbona...@redhat.com To: engine-devel engine-devel@ovirt.org, us...@ovirt.org, VDSM Project Development vdsm-de...@lists.fedorahosted.org, Eduardo Warszawski ewars...@redhat.com, Roy Golan rgo...@redhat.com, Omer Frenkel ofren...@redhat.com, vdsm-devel vdsm-de...@fedorahosted.org Cc: Itamar Heim ih...@redhat.com Sent: Monday, December 9, 2013 11:30:58 AM Subject: Re: [Engine-devel] [QE] oVirt 3.3.2 RC status 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 3 bugs still blocking the release: WhiteboardBug ID Summary 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 3.3.2 backported and wait for review from REST 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. oVirt 3.3.2 beta testing is in progress, thanks to all who already started testing it! For those willing to help testing the bugs, I suggest to add yourself as QA contact for the bug and add yourself to the testing page [3]. 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 ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
[Engine-devel] master is broken by Common#VdcActionUtilsTest ??
[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 RD ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
[Engine-devel] restapi: Permissions in Capabilities (#859225)
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. ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Fwd: [Users] oVirt Cloud-Init integration REST-API
On 12/09/2013 10:08 AM, Sven Kieske wrote: Hi, I appreciate your backport! Are the RPMs in the beta repo also updated? I would test this feature intensive, so you might get valuable feedback. iirc, 3.3.2 is slated to be refreshed wednesday, assuming all blockers are fixed. ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Fwd: [Users] oVirt Cloud-Init integration REST-API
Il 09/12/2013 12:22, Itamar Heim ha scritto: On 12/09/2013 10:08 AM, Sven Kieske wrote: Hi, I appreciate your backport! Are the RPMs in the beta repo also updated? I would test this feature intensive, so you might get valuable feedback. iirc, 3.3.2 is slated to be refreshed wednesday, assuming all blockers are fixed. Well, we can refresh anyway on Wednesday also if not all blockers are fixed, allowing to test the fixed bugs. We'll discuss this on Wednesday sync meeting. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] master is broken by Common#VdcActionUtilsTest ??
On 12/09/2013 01:11 PM, Yair Zaslavsky wrote: - Original Message - From: Michael Pasternak mpast...@redhat.com To: engine-devel engine-devel@ovirt.org Sent: Monday, December 9, 2013 12:47:12 PM Subject: [Engine-devel] master is broken by Common#VdcActionUtilsTest ?? Please provide the commit hash you tried to compile with ? 30ff53078b18063e1ee94f68db11e91d49515e27 thanks. [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
[Engine-devel] Setting cluster CPU
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 ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Setting cluster CPU
On Dec 9, 2013, at 16:01 , Sandro Bonazzola sbona...@redhat.com wrote: 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). The CPU should be set from the first host if None. That is needed for the PPC support. Roy, we talked about it recently, where are we with this patch. Thanks, michal 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 ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Setting cluster CPU
- Original Message - From: Michal Skrivanek michal.skriva...@redhat.com To: Sandro Bonazzola sbona...@redhat.com, Roy Golan rgo...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Monday, December 9, 2013 5:50:49 PM Subject: Re: [Engine-devel] Setting cluster CPU On Dec 9, 2013, at 16:01 , Sandro Bonazzola sbona...@redhat.com wrote: 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). The CPU should be set from the first host if None. That is needed for the PPC support. Roy, we talked about it recently, where are we with this patch. We already support modifying the CPU level of an existing cluster. If changing it to a higher level then we just change it. If changing it to a lower level, and there are running VMs on the cluster, then we warn the user that some VMs might not be migrate-able, as we added a scheduling filter to filter out hosts with improper CPU level. Unless I'm missing something, that covers the use-case, isn't it? Thanks, michal 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 ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Setting cluster CPU
- Original Message - From: Sandro Bonazzola sbona...@redhat.com To: Michal Skrivanek michal.skriva...@redhat.com, Oved Ourfalli ov...@redhat.com, Roy Golan rgo...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Tuesday, December 10, 2013 9:12:14 AM Subject: Re: [Engine-devel] Setting cluster CPU Il 09/12/2013 19:37, Michal Skrivanek ha scritto: On 09 Dec 2013, at 18:58, Oved Ourfalli ov...@redhat.com wrote: - Original Message - From: Michal Skrivanek michal.skriva...@redhat.com To: Sandro Bonazzola sbona...@redhat.com, Roy Golan rgo...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Monday, December 9, 2013 5:50:49 PM Subject: Re: [Engine-devel] Setting cluster CPU On Dec 9, 2013, at 16:01 , Sandro Bonazzola sbona...@redhat.com wrote: 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). The CPU should be set from the first host if None. That is needed for the PPC support. Roy, we talked about it recently, where are we with this patch. We already support modifying the CPU level of an existing cluster. If changing it to a higher level then we just change it. If changing it to a lower level, and there are running VMs on the cluster, then we warn the user that some VMs might not be migrate-able, as we added a scheduling filter to filter out hosts with improper CPU level. Unless I'm missing something, that covers the use-case, isn't it? Not sure. I thought this is None to something, where it should work automatically without specifying anything. Just add an operational host Well, here the issue is that while deploying hosted-engine VM, I'm on a SandyBridge host, with 1 VM running on it (the hosted engine VM). That VM has been created with CPU model Westmere to be able to migrate it to other hosts Westmere compatible. But the Default cluster is automatically set to SandyBridge when I add the host also if I specify Westmere as CPU family in Host parameter. We may be able to set manually the CPU level later somehow, but since we've already asked the user about the CPU level I think we should avoid to ask the user to change it again later. See Bug 1034821 - Hosted-setup asks for CPU type but it doesn't set cluster to that CPU Level You can set the CPU level through the SDK, after you add the host (didn't check that, but see no reason it won't work). Thanks, michal 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 ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
