- Devel - oVirt List Archives

[Engine-devel] Task Manager Introduction and Scope for 3.1
by Moti Asayag 01 Jan '12

01 Jan '12

--=_45c5cd30-e659-4171-b65f-ac455ea09b28 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit The following is a new meeting request: Subject: Task Manager Introduction and Scope for 3.1 Organizer: "Moti Asayag" <masayag(a)redhat.com> Location: "Asia-tlv" <asia-tlv(a)redhat.com> Resources: "Asia-tlv" <asia-tlv(a)redhat.com> Time: Sunday, January 1, 2012, 3:00:00 PM - 4:00:00 PM GMT +02:00 Jerusalem Invitees: ykaul(a)redhat.com; mgoldboi(a)redhat.com; engine-devel(a)ovirt.org *~*~*~*~*~*~*~*~*~* This meeting is about introducing the Task Manager feature for 3.1 and its scope. The feature page could be found here: http://ovirt.org/wiki/Features/TaskManager --=_45c5cd30-e659-4171-b65f-ac455ea09b28 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <html><body><h3>The following is a new meeting request:</h3> <p> <table border='0'> <tr><th align=left>Subject:</th><td>Task Manager Introduction and Scope for 3.1 </td></tr> <tr><th align=left>Organizer:</th><td>"Moti Asayag" <masayag(a)redhat.com> </td></tr> </table> <p> <table border='0'> <tr><th align=left>Location:</th><td>"Asia-tlv" <asia-tlv(a)redhat.com> </td></tr> <tr><th align=left>Resources:</th><td>"Asia-tlv" <asia-tlv(a)redhat.com> </td></tr> <tr><th align=left>Time:</th><td>Sunday, January 1, 2012, 3:00:00 PM - 4:00:00 PM GMT +02:00 Jerusalem </td></tr></table> <p> <table border='0'> <tr><th align=left>Invitees:</th><td>ykaul(a)redhat.com; mgoldboi(a)redhat.com; engine-devel(a)ovirt.org </td></tr> </table> <div>*~*~*~*~*~*~*~*~*~*</div><br>This meeting is about introducing the Task Manager feature for 3.1 and its scope.<br>The feature page could be found here: <br>http://ovirt.org/wiki/Features/TaskManager<br></body></html> --=_45c5cd30-e659-4171-b65f-ac455ea09b28 Content-Type: text/calendar; charset=utf-8; method=REQUEST; name=meeting.ics Content-Transfer-Encoding: 7bit BEGIN:VCALENDAR PRODID:Zimbra-Calendar-Provider VERSION:2.0 METHOD:REQUEST BEGIN:VTIMEZONE TZID:Asia/Jerusalem BEGIN:STANDARD DTSTART:19710101T020000 TZOFFSETTO:+0200 TZOFFSETFROM:+0300 RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=9;BYDAY=2SU TZNAME:IST END:STANDARD BEGIN:DAYLIGHT DTSTART:19710101T020000 TZOFFSETTO:+0300 TZOFFSETFROM:+0200 RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=3;BYDAY=-1FR TZNAME:IDT END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT UID:56e41b37-4811-4d6a-8f58-c688e86024e4 SUMMARY:Task Manager Introduction and Scope for 3.1 LOCATION:"Asia-tlv" <asia-tlv(a)redhat.com> ATTENDEE;CN=Yaniv Kaul;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE: mailto:ykaul@redhat.com ATTENDEE;CN=Moran Goldboim;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=T RUE:mailto:mgoldboi@redhat.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE:mailto:engine- devel(a)ovirt.org ATTENDEE;CN=Asia-tlv;CUTYPE=RESOURCE;ROLE=NON-PARTICIPANT;PARTSTAT=NEEDS-ACT ION;RSVP=TRUE:mailto:asia-tlv@redhat.com ORGANIZER;CN=Moti Asayag:mailto:masayag@redhat.com DTSTART;TZID="Asia/Jerusalem":20120101T150000 DTEND;TZID="Asia/Jerusalem":20120101T160000 STATUS:CONFIRMED CLASS:PUBLIC X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY TRANSP:OPAQUE LAST-MODIFIED:20120101T005200Z DTSTAMP:20120101T005200Z SEQUENCE:0 DESCRIPTION:The following is a new meeting request:\n\nSubject: Task Manager Introduction and Scope for 3.1 \nOrganizer: "Moti Asayag" <masayag(a)redhat.c om> \n\nLocation: "Asia-tlv" <asia-tlv(a)redhat.com> \nResources: "Asia-tlv" < asia-tlv(a)redhat.com> \nTime: Sunday\, January 1\, 2012\, 3:00:00 PM - 4:00:0 0 PM GMT +02:00 Jerusalem\n \nInvitees: ykaul(a)redhat.com\; mgoldboi(a)redhat.c om\; engine-devel(a)ovirt.org \n\n\n*~*~*~*~*~*~*~*~*~*\n\nThis meeting is abo ut introducing the Task Manager feature for 3.1 and its scope.\nThe feature page could be found here: \nhttp://ovirt.org/wiki/Features/TaskManager\n X-ALT-DESC;FMTTYPE=text/html:<html><body><h3>The following is a new meeting request:</h3>\n\n<p>\n<table border='0'>\n<tr><th align=left>Subject:</th><t d>Task Manager Introduction and Scope for 3.1 </td></tr>\n<tr><th align=left >Organizer:</th><td>"Moti Asayag" &lt\;masayag(a)redhat.com&gt\; </td></tr>\n< /table>\n<p>\n<table border='0'>\n<tr><th align=left>Location:</th><td>"Asia -tlv" <asia-tlv(a)redhat.com> </td></tr>\n<tr><th align=left>Resources:</th><t d>"Asia-tlv" <asia-tlv(a)redhat.com> </td></tr>\n<tr><th align=left>Time:</th> <td>Sunday\, January 1\, 2012\, 3:00:00 PM - 4:00:00 PM GMT +02:00 Jerusalem \n </td></tr></table>\n<p>\n<table border='0'>\n<tr><th align=left>Invitees: </th><td>ykaul(a)redhat.com\; mgoldboi(a)redhat.com\; engine-devel(a)ovirt.org </t d></tr>\n</table>\n<div>*~*~*~*~*~*~*~*~*~*</div><br>This meeting is about i ntroducing the Task Manager feature for 3.1 and its scope.<br>The feature pa ge could be found here: <br>http://ovirt.org/wiki/Features/TaskManager<br></ body></html> BEGIN:VALARM ACTION:DISPLAY TRIGGER;RELATED=START:-PT30M DESCRIPTION:Reminder END:VALARM END:VEVENT END:VCALENDAR --=_45c5cd30-e659-4171-b65f-ac455ea09b28--

1 0

[Engine-devel] JBoss RPM vs JBoss zip file
by Ronen Angluster 29 Dec '11

29 Dec '11

Hello, I guess this discussion was being carried offline and i wanted to get the as many opinions as possible about this issue. Currently, we provide the users with 2 methods of handling JBoss AS's deployments: 1. Download the zip file from jboss.org and deploy it wherever the user wishes. 2. Install a specially crafted RPM that is designed & destined to work with the ovirt-engine's RPM set of files. (This is a temporary deployment phase that will end when jboss will release their own set of RPMs) in MHO, i think that the RPM deployment should be used ONLY when installing the ovirt-engine RPMs and not when using the ovirt-engine's git repository for development. especially since deployment to the file system of the host requires root permissions and this is not something that should be a consideration when you're developing code. I think that developers should use the JBoss zip package and deploy it locally, and NOT use the ovirt-engine-jbossas RPM. opinions? Ronen

4 5

[Engine-devel] Stable PCI Addresses DR
by Eli Mesika 27 Dec '11

27 Dec '11

Hi We will have a design review meeting this THU, Dec 29 at 15:00 (GMT+1 , ISRAEL time) regarding the new 3.1 Stable PCI Addresses. Meeting is planned to be 1 Hour. Higher level design doc can be found in our oVirt wiki : http://www.ovirt.org/wiki/Features/Design/StableDeviceAddresses Detailed design will be added prior to the meeting. You are invited to join. == Conference Call Info == * Toll Free Dial-In Number (US & Canada): (800) 451-8679 * International dial-in listed below * Conference Code: 9197544554 If you are not actively participating in the conversation please put your line on mute to make it easier for all participants to hear. *6 -- Mute your line #6 -- Unmute your line Global Access Numbers Local: Australia, Sydney Dial-In #: 0289852326 Austria, Vienna Dial-In #: 012534978196 Belgium, Brussels Dial-In #: 027920405 China Dial-In #: 4006205013 Denmark, Copenhagen Dial-In #: 32729215 Finland, Helsinki Dial-In #: 0923194436 France, Paris Dial-In #: 0170377140 Germany, Berlin Dial-In #: 030300190579 Ireland, Dublin Dial-In #: 014367793 Italy, Milan Dial-In #: 0236269529 Netherlands, Amsterdam Dial-In #: 0207975872 Norway, Oslo Dial-In #: 21033188 Singapore Dial-In #: 64840858 Spain, Barcelona Dial-In #: 935452328 Sweden, Stockholm Dial-In #: 0850513770 Switzerland, Geneva Dial-In #: 0225927881 United Kingdom Dial-In #: 02078970515 United Kingdom Dial-In #: 08445790676 United Kingdom, LocalCall Dial-In #: 08445790678 United States Dial-In #: 2127295016 Global Access Numbers Tollfree: Argentina Dial-In #: 8004441016 Australia Dial-In #: 1800337169 Austria Dial-In #: 0800005898 Bahamas Dial-In #: 18002054776 Bahrain Dial-In #: 80004377 Belgium Dial-In #: 080048325 Brazil Dial-In #: 08008921002 Bulgaria Dial-In #: 008001100236 Chile Dial-In #: 800370228 Colombia Dial-In #: 018009134033 Costa Rica Dial-In #: 08000131048 Cyprus Dial-In #: 80095297 Czech Republic Dial-In #: 800700318 Denmark Dial-In #: 80887114 Dominican Republic Dial-In #: 18887512313 Estonia Dial-In #: 8000100232 Finland Dial-In #: 0800117116 France Dial-In #: 0805632867 Germany Dial-In #: 8006647541 Greece Dial-In #: 00800127562 Hong Kong Dial-In #: 800930349 Hungary Dial-In #: 0680016796 Iceland Dial-In #: 8008967 India Dial-In #: 0008006501533 Indonesia Dial-In #: 0018030179162 Ireland Dial-In #: 1800932401 Israel Dial-In #: 1809462557 Italy Dial-In #: 800985897 Jamaica Dial-In #: 18002050328 Japan Dial-In #: 0120934453 Korea (South) Dial-In #: 007986517393 Latvia Dial-In #: 80003339 Lithuania Dial-In #: 880030479 Luxembourg Dial-In #: 80026595 Malaysia Dial-In #: 1800814451 Mexico Dial-In #: 0018664590915 New Zealand Dial-In #: 0800888167 Norway Dial-In #: 80012994 Panama Dial-In #: 008002269184 Philippines Dial-In #: 180011100991 Poland Dial-In #: 008001210187 Portugal Dial-In #: 800814625 Russian Federation Dial-In #: 81080028341012 Saint Kitts and Nevis Dial-In #: 18002059252 Singapore Dial-In #: 8006162235 Slovak Republic Dial-In #: 0800001441 South Africa Dial-In #: 0800981148 Spain Dial-In #: 800300524 Sweden Dial-In #: 200896860 Switzerland Dial-In #: 800650077 Taiwan Dial-In #: 00801127141 Thailand Dial-In #: 001800656966 Trinidad and Tobago Dial-In #: 18002024615 United Arab Emirates Dial-In #: 8000650591 United Kingdom Dial-In #: 08006948057 United States Dial-In #: 8004518679 Uruguay Dial-In #: 00040190315 Venezuela Dial-In #: 08001627182

1 0

[Engine-devel] vdsm checkConnectivity pitfals
by Roy Golan 26 Dec '11

26 Dec '11

Hi all, VDSM network provisioning api exposes a validity check to know the newly applied changes works. The actual check is comparing the /var/run/vdsm/client.log modified time to the time when the check began and repeats that check after sleeping 1 seconds for X time (where X is connectivityTimeOut) def clientSeen(timeout): start = time.time() while timeout >= 0: if os.stat(constants.P_VDSM_CLIENT_LOG).st_mtime > start: return True time.sleep(1) timeout -= 1 return False Main issues I spot are: 1. In case the host is in maintenance, the caller of the API must generate traffic, concurrently to running api call, and then must join and sync threads to realize when all is done. see http://gerrit.ovirt.org/#change,584 2. locally calling vdsClient also modifies the client.log - we can't rely on that no one will do that during the call. 3. Failure writing to the client log will fail network provisioning! All of the above makes it not very reliable as a check and harder to call, without posing races, as client. Possible alternate solution: 1. We can try to reach the api caller socket in return, maybe use http code 100 ? 2. pass in the API a URL which the VDSM will call. could be a health-check servlet or something similar. Any toughs?

4 4

[Engine-devel] Redunant class of ValueObjectMap ?
by Yair Zaslavsky 23 Dec '11

23 Dec '11

Hi all, Do we need org.ovirt.engine.core.common.queries.ValueObjectMap? Can we use a Java map class directly instead (we had to use this with SOAP WS in the past, prior to current rest-API days)? Yair

3 2

[Engine-devel] Patches that support jboss AS7
by Oved Ourfalli 22 Dec '11

22 Dec '11

Hey, I recently worked on making the proper changes to make the engine code work on Jboss AS7, and it works now! Still needs some testing and probably some more adjustments, but it looks promising. I pushed the commits to gerrit (the first one contains most of the changes, the others are fixes and additions): http://gerrit.ovirt.org/698 (POC - review, don't submit) engine: Jboss-as7 - base commit with jboss-as7 related changes http://gerrit.ovirt.org/699 (POC - review, don't submit) restapi: Jboss-as7 - fix rest api tests http://gerrit.ovirt.org/700 (POC - review, don't submit) engine: Jboss-as7 - Fix utilities to work with jboss as7 http://gerrit.ovirt.org/701 (POC - review, don't submit) engine: Jboss-as7 - Copying the correct jdbc jar to the modules directory I'd be happy to hear your comments. Most changes there were done due to problems I encountered, but feel free to suggest other solutions. Make sure you don't submit this patch yet, as it is a POC, and other changes are needed in order to complete the work on that. These patches work under the latest AS7 version (7.1.0.Beta1b) - http://download.jboss.org/jbossas/7.1/jboss-as-7.1.0.Beta1b/jboss-as-7.1.0.… (The patches currently work only on the version above, as one jar is replaced in the Jboss modules directory to solve LDAP issues). All the versions can be found in: http://www.jboss.org/jbossas/downloads I'm here if you have questions or comments. Thank you, Oved

1 1

[Engine-devel] New oVirt-engine RPMs available
by Ofer Schreiber 21 Dec '11

21 Dec '11

Hi all, We are pleased to announce the availability of the newest release of oVirt-engine RPMs. Thanks to Ronen Angluster, these RPMs include the new "engine-setup" utility, which allows a quick installation of oVirt-engine. In order to install the new RPMs, please follow the instructions described in http://www.ovirt.org/wiki/Installing_ovirt_from_rpm The oVirt-Engine team

1 0

[Engine-devel] API: exposing used/total for images and snapshots
by Geert Jansen 21 Dec '11

21 Dec '11

Hi Michael, i remember that previously we exposed both used and total size for VM images. Right now it seems the API is only exposing total but not used. The GUI is exposing used. Do i remember this correctly? A second question on snapshots: here i think we never showed used/total, and the GUI does not show this either. Do we track this data in the BE, or would this also require backend changes? Please let me know and i'll file the right BZs. Thanks, Geert

1 0

[Engine-devel] ovirt engine bi-weekly meeting
by Livnat Peer 21 Dec '11

21 Dec '11

Hi All, No meeting this week we'll re-sync after the holidays. Livnat

2 1

[Engine-devel] UPDATE: New tool to upload OVF archives
by Keith Robertson 20 Dec '11

20 Dec '11

All, I have updated[1] the ovf uploader in response to some comments in gerrit and to handle some serious Python 2.6 issues. The 2.6 version of ElementTree (i.e. the XML parser) was producing invalid XML. Fortunately, lxml is a drop-in replacement. [1]: http://gerrit.ovirt.org/#change,574 Cheers, Keith

1 0