- Devel - oVirt List Archives

[Engine-devel] F17 maven build failure
by Ofer Schreiber 21 May '12

21 May '12

Hey, I'm trying to build ovirt-engine in Fedora 17, and getting the following error: [INFO] oVirt Modules - manager ........................... FAILURE [1:05.421s] .... [ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:2.6:check (default) on project manager-modules: Execution default of goal org.apache.maven.plugins:maven-checkstyle-plugin:2.6:check failed: Plugin org.apache.maven.plugins:maven-checkstyle-plugin:2.6 or one of its dependencies could not be resolved: The following artifacts could not be resolved: checkstyle:checkstyle:jar:5.0, antlr:antlr:jar:2.7.6, commons-beanutils:commons-beanutils-core:jar:1.7.0, com.google.collections:google-collections:jar:0.9: Could not find artifact checkstyle:checkstyle:jar:5.0 -> [Help 1] Any idea how can I resolve it? --- Ofer Schreiber

2 5

[Engine-devel] port mirroring REST API
by Livnat Peer 21 May '12

21 May '12

Hi All, After digging into the port mirroring feature I suggest a different modeling of it in the API. The current modeling is to add to vnic a boolean property of port-mirroring, e.g. api/vms/{vm-id}/nics <nics> <nic> ... <network href="/api/networks/{network-id}" id="{network-id}"/> <port-mirroring> true </port mirroring> </nic> </VM> This modeling imply 2 limitations: 1. The vnic must be connected to the network it wants to monitor 2. the nic can mirror only a single network Both of the above limitations are correct to the current implementation. Going forward we might want to introduce the above functionalities and the above modeling won't hold. Instead of the above I suggest to change the port-mirroring property to a list of networks. <nics> <nic> ... <network href="/api/networks/{network-id}" id="{network-id}"/> <port-mirroring> <network href="/api/networks/{network-id}" id="{network-id}"/> .... </port mirroring> </nic> </VM> In this version we'll validate that the network under port-mirroring is equal to the network the vnic is connected to, in future versions we can remove this validation without changing the API. Thanks, Livnat

3 7

[Engine-devel] Engine DB - user locked
by Elad Tabak 21 May '12

21 May '12

Hi, After an attempt to clear the DB by running './create_db_devel.sh -u postgres', I got an error: *Failed to create database engine* I then run 'dropdb -U postgres engine', and then 'create_db_devel.sh' again, but still I get the same error. When I tried to login from the admin web interface, I get authentication error. This is from the jboss log: USER_FAILED_TO_AUTHENTICATE_ACCOUNT_IS_LOCKED_OR_DISABLED I also tried running './create_db_devel.sh -u postgres -d engine_new', but it gives the same error ("Failed to create database engine_new"). I tried restarting the posgresql service, it didn't help. Please advice. Thanks, Elad

3 6

[Engine-devel] Advanced Nfs Options + NFSv4 GUI mockup
by Einav Cohen 21 May '12

21 May '12

Please review the mock-up on the feature page: http://www.ovirt.org/wiki/Features/AdvancedNfsOptions#User_Experience Comments are welcome. ---- Thanks, Einav

6 14

[Engine-devel] MAC address validation
by Mike Kolesnik 21 May '12

21 May '12

--=_866d6214-3639-45a0-b94a-0b67e454d998 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hi, We have a bug open on engine to validate MAC address: https://bugzilla.redhat.com/show_bug.cgi?id=756437 The format supported by engine (for Ethernet) is FF:FF:FF:FF:FF:FF (F is any hex char). Is there any other format we must support? Regards, Mike --=_866d6214-3639-45a0-b94a-0b67e454d998 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Times New Roman; font-size: 12pt; color: #000000'>Hi, We have a bug open on engine to validate MAC address: https://bugzilla.redhat.com/show_bug.cgi?id=756437 The format supported by engine (for Ethernet) is FF:FF:FF:FF:FF:FF (F is any hex char). Is there any other format we must support? <div>Regards, Mike </div> </div></body></html> --=_866d6214-3639-45a0-b94a-0b67e454d998--

5 4

[Engine-devel] IMPORTANT: Root web application moved
by Juan Hernandez 20 May '12

20 May '12

Hello, I have recently merged a change that moves the root web application to the .ear directory: http://gerrit.ovirt.org/3782 This change could break your environment if you apply the patch and you don't do a clean installation. You may find an error like this in your server log and the application can fail to deploy: JBAS014777: Services which failed to start: service jboss.web.deployment.default-host./: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./: Failed to start service That means that you have more than one / application. Please make sure that you don't have the old ROOT.war in your deployment directory. Just remove it and the corresponding ROOT.war.dodeploy file. Also make sure that you don't have the following parameter in your standalone.xml file: enable-welcome-root="true" Change the value to "false". None of this actions are needed if you are building new RPMs and doing a clean installation. If you still have problems starting the application server after applying this change please let me know. Regards, Juan Hernandez

2 3

[Engine-devel] DiskImage public mupper
by Michael Pasternak 20 May '12

20 May '12

what should be exposed to user as disk.id: DiskImage.id or DiskImage.ImageId ? -- Michael Pasternak RedHat, ENG-Virtualization R&D

2 4

[Engine-devel] Java 7: Fix namespaces use in OVF writer
by Juan Hernandez 18 May '12

18 May '12

Hello, I recently submitted a change to fix the way we manage namespaces in the OVF writer: http://gerrit.ovirt.org/4540 The problem is that it doesn't work with the StAX reference implementation included with Java 7. With the patched OVF writer I generated the attached OVF file. I would appreciate if someone can take a quick look at it and tell me if it is correct. I would also appreciate if you can send me known good OVF files generated by the engine, to compare them with the ones produced with the patched OVF writer. Thanks in advance, Juan Hernandez -- Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.

2 2

[Engine-devel] Where is the git workspace of "engine-iso-uploader"?
by Shu Ming 18 May '12

18 May '12

Hi, From this page, I am told that it should be in the same workspace as ovirt-engine. http://www.ovirt.org/project/subprojects/ However, I can not find it in ovirt-engine workspace. Where does it go? -- Shu Ming<shuming(a)linux.vnet.ibm.com> IBM China Systems and Technology Laboratory

2 4

[Engine-devel] Feedback requested on name change
by Alex Lourie 17 May '12

17 May '12

This is a multi-part message in MIME format. --------------090408020509030405010906 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit We have now separated tools repositories which are built independently from ovirt-engine, for example "ovirt-image-uploader". Our rpms (ovirt-engine) has a dependency on those tools, using the following option: <snip> ... Requires: %{name}-image-uploader ... <snip> %{name} is substituted by 'ovirt-engine' during build, creating a dependency on "*ovirt-engine-image-uploader*". This, in turn, makes a non-resolved dependency, as the actual package name built for image-uploader is "*ovirt-image-uploader*". We can resolve this by either changing the dependency in our rpms or by changing the tools package names (relevant also for iso-uploader and log-collector). Please let me know which way seems preferable for this. Thanks. -- Alex Lourie. --------------090408020509030405010906 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </head> <body bgcolor="#FFFFFF" text="#000000"> We have now separated tools repositories which are built independently from ovirt-engine, for example "ovirt-image-uploader". Our rpms (ovirt-engine) has a dependency on those tools, using the following option: <snip> ... Requires: %{name}-image-uploader ... <snip> %{name} is substituted by 'ovirt-engine' during build, creating a dependency on "ovirt-engine-image-uploader". This, in turn, makes a non-resolved dependency, as the actual package name built for image-uploader is "ovirt-image-uploader". We can resolve this by either changing the dependency in our rpms or by changing the tools package names (relevant also for iso-uploader and log-collector). Please let me know which way seems preferable for this. Thanks. <pre class="moz-signature" cols="72">-- Alex Lourie.</pre> </body> </html> --------------090408020509030405010906--

2 1