- Devel - oVirt List Archives

[Engine-devel] Proposal for support ISO domain on other types of file based storage.
by Mark Wu 18 Mar '13

18 Mar '13

This is a multi-part message in MIME format. --------------070305010507040809030004 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi guys, Currently, ISO domain is only supported on NFS storage. It could improve the ease of use if it allows other types of file based storage to store ISO images. After an investigation, I found there's not any restriction on this idea. So the whole work is removing the limitation on engine side. That means engine should allow ISO domain could have different storage type from the data center it's attached, like what we do with nfs ISO domain in SAN DC. I start this idea with localfs. I know local storage can't be seen in cluster level. But it also provides a choice if no NFS available. VMs can be created on the host which has the ISO repo, and then be migrated to any other host in the cluster. I have done the initial patches: allow creation ISO domain on localfs [1] and support import ISO domain on localfs [2] I don't have much experience in java/j2ee/web development and engine architecture. The patches just work for me. I am not sure if it will bring some potential problems. So any feedback on the patch or the idea will be appreciated very much. Mark. [1] http://gerrit.ovirt.org/#/c/12687/ [2] http://gerrit.ovirt.org/#/c/12916/ --------------070305010507040809030004 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"> Hi guys, <br> <br> Currently, ISO domain is only supported on NFS storage.  It could improve the ease of use if it allows other types<br> of file based storage to store ISO images. After an investigation,  I found there's not any restriction on this idea.<br> So the whole work is removing the limitation on engine side.  That means engine should allow ISO domain could <br> have different storage type from the data center it's attached, like what we do with nfs ISO domain in SAN DC.<br> <br> I start this idea with localfs. I know local storage can't be seen in cluster level. But it also provides a choice if no<br> NFS available. VMs can be created on the host which has the ISO repo, and then be migrated to any other host in the cluster.<br> I have done the initial patches: allow creation ISO domain on localfs [1] and support import ISO domain on localfs [2]<br> I don't have much experience in java/j2ee/web development and engine architecture.  The patches just work for me.<br> I am not sure if it will bring some potential problems.  So any feedback on the patch or  the idea will be appreciated very much.<br> <br> <br> Mark.<br> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> <br> [1] <a href="http://gerrit.ovirt.org/#/c/12687/">http://gerrit.ovirt.org/#/c/12687/</a><br> [2] <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> <a href="http://gerrit.ovirt.org/#/c/12916/">http://gerrit.ovirt.org/#/c/12916/<br> </a> </body> </html> --------------070305010507040809030004--

3 9

[Engine-devel] make rpm error: No targets specified and no makefile found. Stop
by qyddbear 18 Mar '13

18 Mar '13

------=_Part_279309_491577683.1363594708599 Content-Type: text/plain; charset=GBK Content-Transfer-Encoding: 7bit Hi, I am a green learner, I tried to make ovirt-engine rpm from compiled source code. when I run make rpm, and the log as follows. Can anyone tell me what's the matter? Thanks! [root@localhost ovirt-engine-3.1.0]# make rpm sed -e 's/@PACKAGE_VERSION@/3.1.0/g' \ -e 's/@PACKAGE_RELEASE@/3.26/g' packaging/fedora/spec/ovirt-engine.spec.in > ovirt-engine.spec git ls-files | tar --files-from /proc/self/fd/0 -czf ovirt-engine-3.1.0.tar.gz ovirt-engine.spec rm -f ovirt-engine.spec You can use rpmbuild -tb ovirt-engine-3.1.0.tar.gz to produce rpms rm -rf /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild mkdir -p /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/{SPECS,RPMS,SRPMS,SOURCES,BUILD,BUILDROOT} mkdir -p output rpmbuild -ts --define="_topdir /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild" ovirt-engine-3.1.0.tar.gz Wrote: /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/SRPMS/ovirt-engine-3.1.0-3.26.el6.src.rpm mv /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/SRPMS/*.rpm output rm -rf /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild srpm is ready at output rm -rf /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild mkdir -p /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/{SPECS,RPMS,SRPMS,SOURCES,BUILD,BUILDROOT} mkdir -p output rpmbuild --define="_topdir /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild" --rebuild output/ovirt-engine-3.1.0*.src.rpm Installing output/ovirt-engine-3.1.0-3.26.el6.src.rpm Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.3JQHHM + umask 022 + cd /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/BUILD + LANG=C + export LANG + unset DISPLAY + cd /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/BUILD + rm -rf ovirt-engine-3.1.0 + /bin/mkdir -p ovirt-engine-3.1.0 + cd ovirt-engine-3.1.0 + /bin/tar -xf - + /usr/bin/gzip -dc /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/SOURCES/ovirt-engine-3.1.0.tar.gz + STATUS=0 + '[' 0 -ne 0 ']' + /bin/chmod -Rf a+rX,u+w,g-w,o-w . + exit 0 Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.qesWT3 + umask 022 + cd /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/BUILD + cd ovirt-engine-3.1.0 + LANG=C + export LANG + unset DISPLAY + make -j1 PACKAGE_NAME=ovirt-engine ENGINE_NAME=ovirt-engine LOCALSTATE_DIR=/var ENGINE_STATE=/var/lib/ovirt-engine PREFIX=/usr SYSCONF_DIR=/etc BIN_DIR=/usr/bin DATAROOT_DIR=/usr/share MAN_DIR=/usr/share/man PYTHON=/usr/bin/python PYTHON_DIR=/usr/lib/python2.6/site-packages JAVA_DIR=/usr/share/java MAVENPOM_DIR=/usr/share/maven2/poms PKG_JAVA_DIR=/usr/share/java/ovirt-engine PKG_SYSCONF_DIR=/etc/ovirt-engine PKG_EAR_DIR=/usr/share/ovirt-engine/engine.ear PKG_PKI_DIR=/etc/pki/ovirt-engine PKG_JBOSS_MODULES=/usr/share/ovirt-engine/modules make[1]: Entering directory `/home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/BUILD/ovirt-engine-3.1.0' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory `/home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/BUILD/ovirt-engine-3.1.0' error: Bad exit status from /var/tmp/rpm-tmp.qesWT3 (%build) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.qesWT3 (%build) make: *** [rpm] Error 1 There is a ovirt-engine.spec under /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/BUILD/ovirt-engine-3.1.0 ------=_Part_279309_491577683.1363594708599 Content-Type: text/html; charset=GBK Content-Transfer-Encoding: 7bit <div style="line-height:1.7;color:#000000;font-size:14px;font-family:arial"><div style="line-height:1.7;color:#000000;font-size:14px;font-family:arial"><div>Hi, I am a green learner, I tried to make ovirt-engine rpm from compiled source code. when I run make rpm, and the log as follows. Can anyone tell me what's the matter? Thanks!</div><div><br></div><div>[root@localhost ovirt-engine-3.1.0]# make rpm</div><div><span style="background-color: rgb(192, 192, 192);">sed -e 's/@PACKAGE_VERSION@/3.1.0/g' \</span></div><div><span style="background-color: rgb(192, 192, 192);">            -e 's/@PACKAGE_RELEASE@/3.26/g' packaging/fedora/spec/ovirt-engine.spec.in > ovirt-engine.spec</span></div><div><span style="background-color: rgb(192, 192, 192);">git ls-files | tar --files-from /proc/self/fd/0 -czf ovirt-engine-3.1.0.tar.gz ovirt-engine.spec</span></div><div><span style="background-color: rgb(192, 192, 192);">rm -f ovirt-engine.spec</span></div><div><span style="background-color: rgb(192, 192, 192);"><br></span></div><div><span style="background-color: rgb(192, 192, 192);">You can use rpmbuild -tb ovirt-engine-3.1.0.tar.gz to produce rpms</span></div><div><span style="background-color: rgb(192, 192, 192);"><br></span></div><div><span style="background-color: rgb(192, 192, 192);">rm -rf /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild</span></div><div><span style="background-color: rgb(192, 192, 192);">mkdir -p /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/{SPECS,RPMS,SRPMS,SOURCES,BUILD,BUILDROOT}</span></div><div><span style="background-color: rgb(192, 192, 192);">mkdir -p output</span></div><div><span style="background-color: rgb(192, 192, 192);">rpmbuild -ts --define="_topdir /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild" ovirt-engine-3.1.0.tar.gz</span></div><div><span style="background-color: rgb(192, 192, 192);">Wrote: /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/SRPMS/ovirt-engine-3.1.0-3.26.el6.src.rpm</span></div><div><span style="background-color: rgb(192, 192, 192);">mv /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/SRPMS/*.rpm output</span></div><div><span style="background-color: rgb(192, 192, 192);">rm -rf /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild</span></div><div><span style="background-color: rgb(192, 192, 192);"><br></span></div><div><span style="background-color: rgb(192, 192, 192);">srpm is ready at output</span></div><div><span style="background-color: rgb(192, 192, 192);"><br></span></div><div><span style="background-color: rgb(192, 192, 192);">rm -rf /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild</span></div><div><span style="background-color: rgb(192, 192, 192);">mkdir -p /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/{SPECS,RPMS,SRPMS,SOURCES,BUILD,BUILDROOT}</span></div><div><span style="background-color: rgb(192, 192, 192);">mkdir -p output</span></div><div><span style="background-color: rgb(192, 192, 192);">rpmbuild --define="_topdir /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild"  --rebuild output/ovirt-engine-3.1.0*.src.rpm</span></div><div><span style="background-color: rgb(192, 192, 192);">Installing output/ovirt-engine-3.1.0-3.26.el6.src.rpm</span></div><div><span style="background-color: rgb(192, 192, 192);">Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.3JQHHM</span></div><div><span style="background-color: rgb(192, 192, 192);">+ umask 022</span></div><div><span style="background-color: rgb(192, 192, 192);">+ cd /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/BUILD</span></div><div><span style="background-color: rgb(192, 192, 192);">+ LANG=C</span></div><div><span style="background-color: rgb(192, 192, 192);">+ export LANG</span></div><div><span style="background-color: rgb(192, 192, 192);">+ unset DISPLAY</span></div><div><span style="background-color: rgb(192, 192, 192);">+ cd /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/BUILD</span></div><div><span style="background-color: rgb(192, 192, 192);">+ rm -rf ovirt-engine-3.1.0</span></div><div><span style="background-color: rgb(192, 192, 192);">+ /bin/mkdir -p ovirt-engine-3.1.0</span></div><div><span style="background-color: rgb(192, 192, 192);">+ cd ovirt-engine-3.1.0</span></div><div><span style="background-color: rgb(192, 192, 192);">+ /bin/tar -xf -</span></div><div><span style="background-color: rgb(192, 192, 192);">+ /usr/bin/gzip -dc /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/SOURCES/ovirt-engine-3.1.0.tar.gz</span></div><div><span style="background-color: rgb(192, 192, 192);">+ STATUS=0</span></div><div><span style="background-color: rgb(192, 192, 192);">+ '[' 0 -ne 0 ']'</span></div><div><span style="background-color: rgb(192, 192, 192);">+ /bin/chmod -Rf a+rX,u+w,g-w,o-w .</span></div><div><span style="background-color: rgb(192, 192, 192);">+ exit 0</span></div><div><span style="background-color: rgb(192, 192, 192);">Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.qesWT3</span></div><div><span style="background-color: rgb(192, 192, 192);">+ umask 022</span></div><div><span style="background-color: rgb(192, 192, 192);">+ cd /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/BUILD</span></div><div><span style="background-color: rgb(192, 192, 192);">+ cd ovirt-engine-3.1.0</span></div><div><span style="background-color: rgb(192, 192, 192);">+ LANG=C</span></div><div><span style="background-color: rgb(192, 192, 192);">+ export LANG</span></div><div><span style="background-color: rgb(192, 192, 192);">+ unset DISPLAY</span></div><div><span style="background-color: rgb(192, 192, 192);">+ make -j1 PACKAGE_NAME=ovirt-engine ENGINE_NAME=ovirt-engine LOCALSTATE_DIR=/var ENGINE_STATE=/var/lib/ovirt-engine PREFIX=/usr SYSCONF_DIR=/etc BIN_DIR=/usr/bin DATAROOT_DIR=/usr/share MAN_DIR=/usr/share/man PYTHON=/usr/bin/python PYTHON_DIR=/usr/lib/python2.6/site-packages JAVA_DIR=/usr/share/java MAVENPOM_DIR=/usr/share/maven2/poms PKG_JAVA_DIR=/usr/share/java/ovirt-engine PKG_SYSCONF_DIR=/etc/ovirt-engine PKG_EAR_DIR=/usr/share/ovirt-engine/engine.ear PKG_PKI_DIR=/etc/pki/ovirt-engine PKG_JBOSS_MODULES=/usr/share/ovirt-engine/modules</span></div><div><span style="background-color: rgb(192, 192, 192);">make[1]: Entering directory `/home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/BUILD/ovirt-engine-3.1.0'</span></div><div><b style="background-color: rgb(192, 192, 192);">make[1]: *** No targets specified and no makefile found.  Stop.</b></div><div><span style="background-color: rgb(192, 192, 192);">make[1]: Leaving directory `/home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/BUILD/ovirt-engine-3.1.0'</span></div><div><span style="background-color: rgb(192, 192, 192);">error: Bad exit status from /var/tmp/rpm-tmp.qesWT3 (%build)</span></div><div><span style="background-color: rgb(192, 192, 192);"><br></span></div><div><span style="background-color: rgb(192, 192, 192);"><br></span></div><div><span style="background-color: rgb(192, 192, 192);">RPM build errors:</span></div><div><span style="background-color: rgb(192, 192, 192);">    Bad exit status from /var/tmp/rpm-tmp.qesWT3 (%build)</span></div><div><span style="background-color: rgb(192, 192, 192);">make: *** [rpm] Error 1</span></div><div><br></div><div><br></div><div>There is a ovirt-engine.spec under /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/BUILD/ovirt-engine-3.1.0 </div><div><br></div><div><br></div></div></div><br><br><span title="neteasefooter"><span id="netease_mail_footer"></span></span> ------=_Part_279309_491577683.1363594708599--

2 3

[Engine-devel] CreateComputerAccount - do we really need it?
by Yair Zaslavsky 17 Mar '13

17 Mar '13

Hi all, Do we need CreateComputerAccountCommand and its correspoding ldap broker LdapCreateComputerAccountCommand? Thanks, Yair

4 5

[Engine-devel] Better testing for ValidationResults using ValidationResultMatchers
by Mike Kolesnik 17 Mar '13

17 Mar '13

------=_Part_1902201_1683252520.1363512635975 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hi, If you don't know what ValidationResult is, check out http://www.ovirt.org/ValidationResult In a gist, I added a new way to test this using JUnit's assertThat syntax: // Test that validation result is valid assertThat(someValidation(), isValid()); // Test that validation result is invalid assertThat(someValidation(), failsWith(VdcBllMessages.SOME_ERROR)); // Test that validation result is invalid and has replacement assertThat(someValidation(), both(failsWith(VdcBllMessages.SOME_ERROR)).and(replacements(hasItem(EXPECTED_REPLACEMENT)))); You need to statically import ValidationResultMatchers (and the basic JUnit matchers) for this to work. The rest I documented in the aforementioned wiki. Check out the patch: http://gerrit.ovirt.org/#/c/13061 Or how to use it: http://gerrit.ovirt.org/#/c/13062 Regards, Mike ------=_Part_1902201_1683252520.1363512635975 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,new york,times,serif; font-size: 12pt; color: #000000'>Hi,<br><br>If you don't know what ValidationResult is, check out http://www.ovirt.org/ValidationResult<br><br>In a gist, I added a new way to test this using JUnit's assertThat syntax:<br><pre>// Test that validation result is valid assertThat(someValidation(), isValid()); // Test that validation result is invalid assertThat(someValidation(), failsWith(VdcBllMessages.SOME_ERROR)); // Test that validation result is invalid and has replacement assertThat(someValidation(), both(failsWith(VdcBllMessages.SOME_ERROR)).and(replacements(hasItem(EXPECTED_REPLACEMENT)))); </pre>You need to statically import ValidationResultMatchers (and the basic JUnit matchers) for this to work.<br><br>The rest I documented in the aforementioned wiki.<br><br>Check out the patch: http://gerrit.ovirt.org/#/c/13061<br><br>Or how to use it: http://gerrit.ovirt.org/#/c/13062<br><br><div><span name="x"></span>Regards,<br>Mike<span name="x"></span><br></div><br></div></body></html> ------=_Part_1902201_1683252520.1363512635975--

1 0

[Engine-devel] Generic "name is used" message
by Mike Kolesnik 17 Mar '13

17 Mar '13

------=_Part_1894359_617512914.1363509997819 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hi, Lately I had to add an error message that "name is already used". I looked in the translations files and saw many messages for specific entity types in the system that looked much the same: VDS_TRY_CREATE_WITH_EXISTING_PARAMS=Cannot ${action} ${type}. Host with the same name already exists ACTION_TYPE_FAILED_VM_ALREADY_EXIST = Cannot $ { action } $ { type }. VM with the same name already exists . etc.. What I decided to do is not add another "X with the same name already exists" message, but instead add a generic message for this condition. You can review the patch here : http://gerrit.ovirt.org/#/c/12361 I also went the extra mile to change the current messages that look like this to use this message: http://gerrit.ovirt.org/#/c/13063/ It is not a full coverage, since some commands don't fill the $action $type replacements, and the required change is a bit bigger than this patch scope, but it's a good start. FYI, and if you see other generic messages repeating themselves, don't hesitate to squash them. Regards, Mike ------=_Part_1894359_617512914.1363509997819 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html><head><style type=3D'text/css'>p { margin: 0; }</style></head><body><= div style=3D'font-family: times new roman,new york,times,serif; font-size: = 12pt; color: #000000'>Hi,<br><br>Lately I had to add an error message that = "name is already used".<br>I looked in the translations files and saw many = messages for specific entity types in the system that looked much the same:= <br><span class=3D"str">VDS_TRY_CREATE_WITH_EXISTING_PARAMS=3DCannot ${acti= on} ${type}. Host with the same name already exists<br></span><span class= =3D"pln">ACTION_TYPE_FAILED_VM_ALREADY_EXIST</span><span class=3D"pun">=3D<= /span><span class=3D"typ">Cannot</span><span class=3D"pln"> $</span><span c= lass=3D"pun">{</span><span class=3D"pln">action</span><span class=3D"pun">}= </span><span class=3D"pln"> $</span><span class=3D"pun">{</span><span class= =3D"pln">type</span><span class=3D"pun">}.</span><span class=3D"pln"> VM </= span><span class=3D"kwd">with</span><span class=3D"pln"> the same name alre= ady exists</span><span class=3D"pun">.</span><br>etc..<br><br>What I decide= d to do is not add another "X with the same name already exists" message,<b= r>but instead add a generic message for this condition.<br><br>You can revi= ew the patch here:<br>http://gerrit.ovirt.org/#/c/12361<br><br>I also went = the extra mile to change the current messages that look like this to use th= is message:<br>http://gerrit.ovirt.org/#/c/13063/<br><br>It is not a full c= overage, since some commands don't fill the $action $type replacements,<br>= and the required change is a bit bigger than this patch scope, but it's a g= ood start.<br><br>FYI, and if you see other generic messages repeating them= selves, don't hesitate to squash them.<br><br><div><span name=3D"x"></span>= Regards,<br>Mike<span name=3D"x"></span><br></div><br></div></body></html> ------=_Part_1894359_617512914.1363509997819--

1 0

[Engine-devel] DB Performance Monitoring
by Libor Spevak 15 Mar '13

15 Mar '13

Hi, I just wanted to share a partial result from testing of engine db load during operation (SQL queries frequencies). Maybe, we can decide later, if some SQL queries result CACHING can boost throughput for larger deployments. The caching technology can be from a simple HashMap lookup to deployments of something like http://ehcache.org/ (memory database). I prepared two simple scenarios: - oVirt engine, 2 hosts, 1 VM, running 15 minutes (Power on + Up state) - oVirt engine, 2 hosts, 10 VMs from one pool, running 15 minutes (Power on + Up state) Appending 2 spreadsheets with data about the most used SQL queries (generated by PostgreSQL standard pg_statements_stat module). e.g. - 2nd row shows number of granted connections from the db pool (e.g. can be used to set optimal connection pool size) (check of connection health: select 1) - most of the queries are wrapped by a PLSQL function so we see a wrapper: /select * from getvdsgroupbyvdsgroupid($1, $2, $3)/ and near to it the 'real' query: /SELECT vds_groups_view.*// // FROM vds_groups_view// // WHERE vds_group_id = v_vds_group_id// // AND (NOT v_is_filtered OR EXISTS (SELECT 1// // FROM user_vds_groups_permissions_view// // WHERE user_id = v_user_id AND entity_id = v_vds_group_id))// / Just as an example, I selected in yellow color some queries, which probably do not change often, but are very frequent. Other tools like 'pg_top' can provide runtime statistics of db processes (cpu, mem, locks, ... views). By enabling debug level logging of PostgreSQL we can check real values to the queries. Of course, it would be useful to run such tests with many hosts and VMs to predict scaling issues. More info about tools configuration: http://www.ovirt.org/Engine_database_performance_monitoring Regards, Libor

5 6

[Engine-devel] [EL6 RPMS] new nightly ovirt rpms
by Eyal Edri 14 Mar '13

14 Mar '13

fyi, EL6 rpms for various ovirt project are now available via the nightly repos: http://resources.ovirt.org/releases/nightly/rpm/EL/6/noarch/ Eyal.

1 0

[Engine-devel] engine watchdog support - new version in gerrit
by Laszlo Hornyak 14 Mar '13

14 Mar '13

hi, A new version of the engine watchdog support is available in gerrit. This version finished the rest-api support by adding the capabilities resources. The features listed in the feature page are ready, so if you have enough time and courage, please give it a try! I have left the patch with [wip] because I am waiting for the end of some discussions about the technical background. http://gerrit.ovirt.org/#/c/12419/ Thx, Laszlo

2 1

Re: [Engine-devel] [oVirt Jenkins] ovirt_engine_find_bugs - Build # 3737 - Still Unstable!
by Eyal Edri 14 Mar '13

14 Mar '13

Latest commit introduced new NORMAL findbugs, please fix. eyal. infra team. ----- Original Message ----- > From: "Jenkins ci oVirt Server" <jenkins(a)ovirt.org> > To: eedri(a)redhat.com, engine-patches(a)ovirt.org, oliel(a)redhat.com, yzaslavs(a)redhat.com, dcaro(a)redhat.com, > gerrit2(a)gerrit.ovirt.org > Sent: Thursday, March 14, 2013 12:32:10 AM > Subject: [oVirt Jenkins] ovirt_engine_find_bugs - Build # 3737 - Still Unstable! > > Project: http://jenkins.ovirt.org/job/ovirt_engine_find_bugs/ > Build: http://jenkins.ovirt.org/job/ovirt_engine_find_bugs/3737/ > Build Number: 3737 > Build Status: Still Unstable > Triggered By: Started by an SCM change > > ------------------------------------- > Changes Since Last Success: > ------------------------------------- > Changes for Build #3733 > [Michael Kublin] engine: Making all internal actions to have same > correlationId > > > Changes for Build #3734 > [Gerrit Code Review] webadmin: Attach disk - verify valid selection > > [Gerrit Code Review] webadmin: Make Template dialog - style > modifications > > [Gerrit Code Review] webadmin: About dialog - remove redundant code > > > Changes for Build #3735 > [Allon Mureinik] core: AuditLogableBaseTest synthetic access > > [Allon Mureinik] core: TestAuditLoggableBase serial warning > > > Changes for Build #3736 > [Kiril Nesenko] webadmin: Change default doc path. > > > Changes for Build #3737 > [Gerrit Code Review] db: do not write to dbscripts after installation > > > > > ----------------- > Failed Tests: > ----------------- > No tests ran. > >

1 0

[Engine-devel] Async Task Manager improvements
by Yair Zaslavsky 14 Mar '13

14 Mar '13

Hi all, I would like to present you a document I'm working on (still in draft/working-in-progress mode) of changes to be done at the engine async task manager. Regarding the detailed design - The suggested design breaks the task management into two modules - task management/polling part + command management (in context of completion of tasks/commands). The current status of the design is that the design of task management is provided (needs some polishing) - the command management design will be provided soon. In addition, we already have some ideas for an alternative design for the task management part (as suggested by Saggi Mizrahi). After converging , we will present the complete design. The reason we're sending the Wiki now is that community members will be aware mainly to the motivations behind the changes (Perhaps we should create separate documents for the design and for the motivation/requirements) http://www.ovirt.org/Wiki/AsyncTaskManagerChanges Yair

2 2