- Devel - oVirt List Archives

[Engine-devel] [oVirt 3.3 Localization Question #5] "cloudInitAttachmentContentBase64ToolTip"
by Yuko Katabami 03 Aug '13

03 Aug '13

This is a multi-part message in MIME format. --------------020604030100000408050001 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi all, I would like to ask you a localization-related question. Could anyone help me with the following?: *File:***CommonApplicationConstants* **Resource ID: *cloudInitAttachmentContentBase64ToolTip* **String:***Enter the attachment content encoded in base-64* **Question:* Is this referring to the new feature described at: http://www.ovirt.org/Features/Cloud-Init_Integration ? If so, "attachment" in this case is about file(s) to attach (inject) to the guest disk? It would be helpful if you could also tell me how to navigate to this GUI label in the Admin Portal, if it is already available. Thank you, Yuko -- Regards, Yuko Katabami (?????) Technical Translator II NAATI Accredited Professional Translator (English into Japanese) #28138 RHCSA #111-119-244 *Mobile:* +61 415 847 352 *Email:* ykatabam(a)redhat.com Red Hat *Red Hat, Asia-Pacific Pty Ltd* Level 1, 193 North Quay Brisbane 4000 *Office:* +61 7 3514 8100 *Fax:* +61 7 3514 8199 *Website:* www.redhat.com <http://www.redhat.com> *Facebook:* Red Hat APAC <http://www.facebook.com/redhatapac> | Red Hat Japan <http://www.facebook.com/redhatjapan> | Red Hat Korea <http://www.facebook.com/redhatkorea> | JBoss APAC <http://www.facebook.com/JBossAPAC> *Twitter:* Red Hat APAC <http://www.twitter.com/red_hat_apac> | Red Hat ANZ <http://www.twitter.com/redhatanz> *LinkedIn:* Red Hat APAC <http://www.linkedin.com/groups?gid=3124596> | JBoss APAC <http://www.linkedin.com/groups?gid=4068303> --------------020604030100000408050001 Content-Type: multipart/related; boundary="------------050901040307010200050409" --------------050901040307010200050409 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 all, <br> <br> I would like to ask you a localization-related question.<br> Could anyone help me with the following?:<br> <br> <b>File:</b><b> </b>CommonApplicationConstants<b><br> </b><b>Resource ID: </b>cloudInitAttachmentContentBase64ToolTip<b><br> </b><b>String:</b><b> </b>Enter the attachment content encoded in base-64<b><br> </b><b>Question:</b> Is this referring to the new feature described at: <a href="http://www.ovirt.org/Features/Cloud-Init_Integration" title="http://www.ovirt.org/Features/Cloud-Init_Integration">http://www.ovirt.org/Features/Cloud-Init_Integration</a> ?<br> If so, "attachment" in this case is about file(s) to attach (inject) to the guest disk? <br> It would be helpful if you could also tell me how to navigate to this GUI label in the Admin Portal<span class="gwt-InlineLabel">, if it is already available.<br> <br> Thank you,<br> <br> Yuko<br> </span> <div class="moz-signature">-- <br> <font color="#000000" face="arial, sans-serif" size="2"> Regards, <br> <br> Yuko Katabami (方波見裕子) <br> Technical Translator II <br> NAATI Accredited Professional Translator (English into Japanese) #28138 <br> RHCSA #111-119-244 <br> <b>Mobile:</b> +61 415 847 352 <br> <b>Email:</b> <a class="moz-txt-link-abbreviated" href="mailto:ykatabam@redhat.com">ykatabam(a)redhat.com</a> <br> <br> <a target="_blank"><img src="cid:part2.03050806.06010500@redhat.com" alt="Red Hat" height="42" border="0" width="128"></a> <br> <br> <b>Red Hat, Asia-Pacific Pty Ltd</b> <br> Level 1, 193 North Quay <br> Brisbane 4000 <br> <b>Office:</b> +61 7 3514 8100 <br> <b>Fax:</b> +61 7 3514 8199 <br> <b>Website:</b> <a href="http://www.redhat.com" target="_blank">www.redhat.com</a> <br> <br> <b>Facebook:</b> <a href="http://www.facebook.com/redhatapac" target="_blank">Red Hat APAC</a> | <a href="http://www.facebook.com/redhatjapan" target="_blank">Red Hat Japan</a> | <a href="http://www.facebook.com/redhatkorea" target="_blank">Red Hat Korea</a> | <a href="http://www.facebook.com/JBossAPAC" target="_blank">JBoss APAC</a> <br> <b>Twitter:</b> <a href="http://www.twitter.com/red_hat_apac" target="_blank">Red Hat APAC</a> | <a href="http://www.twitter.com/redhatanz" target="_blank">Red Hat ANZ</a> <br> <b>LinkedIn:</b> <a href="http://www.linkedin.com/groups?gid=3124596" target="_blank">Red Hat APAC</a> | <a href="http://www.linkedin.com/groups?gid=4068303" target="_blank">JBoss APAC</a> </font> </div> </body> </html> --------------050901040307010200050409 Content-Type: image/png; name="redhat-logo.png" Content-Transfer-Encoding: base64 Content-ID: <part2.03050806.06010500(a)redhat.com> Content-Disposition: inline; filename="redhat-logo.png" iVBORw0KGgoAAAANSUhEUgAAAIAAAAApCAYAAAD9LSHtAAAAGXRFWHRTb2Z0d2FyZQBBZG9i ZSBJbWFnZVJlYWR5ccllPAAAA6NpVFh0WE1MOmNvbS5hZG9iZS54bXAAAAAAADw/eHBhY2tl dCBiZWdpbj0i77u/IiBpZD0iVzVNME1wQ2VoaUh6cmVTek5UY3prYzlkIj8+IDx4OnhtcG1l dGEgeG1sbnM6eD0iYWRvYmU6bnM6bWV0YS8iIHg6eG1wdGs9IkFkb2JlIFhNUCBDb3JlIDUu MC1jMDYxIDY0LjE0MDk0OSwgMjAxMC8xMi8wNy0xMDo1NzowMSAgICAgICAgIj4gPHJkZjpS REYgeG1sbnM6cmRmPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5LzAyLzIyLXJkZi1zeW50YXgt bnMjIj4gPHJkZjpEZXNjcmlwdGlvbiByZGY6YWJvdXQ9IiIgeG1sbnM6eG1wTU09Imh0dHA6 Ly9ucy5hZG9iZS5jb20veGFwLzEuMC9tbS8iIHhtbG5zOnN0UmVmPSJodHRwOi8vbnMuYWRv YmUuY29tL3hhcC8xLjAvc1R5cGUvUmVzb3VyY2VSZWYjIiB4bWxuczp4bXA9Imh0dHA6Ly9u cy5hZG9iZS5jb20veGFwLzEuMC8iIHhtbG5zOmRjPSJodHRwOi8vcHVybC5vcmcvZGMvZWxl bWVudHMvMS4xLyIgeG1wTU06RG9jdW1lbnRJRD0ieG1wLmRpZDpDMTM3NDQ3MkZCQzExMUUw OTQzNzk0QTNCNkFFNjg1RCIgeG1wTU06SW5zdGFuY2VJRD0ieG1wLmlpZDpDMTM3NDQ3MUZC QzExMUUwOTQzNzk0QTNCNkFFNjg1RCIgeG1wOkNyZWF0b3JUb29sPSJBZG9iZSBJbGx1c3Ry YXRvciBDUzMiPiA8eG1wTU06RGVyaXZlZEZyb20gc3RSZWY6aW5zdGFuY2VJRD0idXVpZDpD QzZBQjQzODY4MDNERDExOENBRDk2OTlCQTZCNjM4OSIgc3RSZWY6ZG9jdW1lbnRJRD0idXVp ZDpDQjZBQjQzODY4MDNERDExOENBRDk2OTlCQTZCNjM4OSIvPiA8ZGM6dGl0bGU+IDxyZGY6 QWx0PiA8cmRmOmxpIHhtbDpsYW5nPSJ4LWRlZmF1bHQiPnJlZGhhdF9jbXlrX2xvZ288L3Jk ZjpsaT4gPC9yZGY6QWx0PiA8L2RjOnRpdGxlPiA8L3JkZjpEZXNjcmlwdGlvbj4gPC9yZGY6 UkRGPiA8L3g6eG1wbWV0YT4gPD94cGFja2V0IGVuZD0iciI/Pv93CnUAAA4OSURBVHja7FwL dBTVGf5ms49kySYkgSQkIZCkvKLyCCAIEQRFLdIiqPUN4qsitmhFQKgWKlpRQT1HsEINePBR hfr2+ECUtAoICCggGEKCEEkC5EFeu9nN7vS/s/+SyWR2s4mBgGf/cz4ye+femdn7f/d/3Vkk tE0MhPMJowgXEXoRkgidCDJBItgJxYQCwhbCRsL3BBdCcs5KLGEGYSuhgZUdLDyE3YQ5hITQ VJ5bEk54kFe03A4oJywgRIWm9uyX4YRdzZVo0EBSwffZ11fSfD6FPMKloSnuOJFaOC/M/RKC RT0kMtyM0amJSDYZ4ZJlFLvcOFJrR62rARFGI/pEWTHYYkKiLMFEIwpJ9+9X1GDnkRLWexMR ruFRwuMhdZxdBHiS/XVTX0BKX9o3HVdUS6RK73AXHdUpQYEMM7W5jMCOCBnbPA04aHeid4QF 1zUY8ZzswEd5h/VIIORFwr0hlZxZCfPT/hRhtl7wPy4jBTPtJtTTpypSpIPgIqVLyllJUa2b rEKCE4iwGLD6cDE2HS1D/+RY/NFhwnqzjPJah949hxISCR+F1NKxBLiPsMjfgBtTuiLFKWGX TUZvpwERpPRwholQr1zUS4gCCh37xNpwd3wchpHFsJFLkOMikFta7u/yQ9gqbQyppmNcwEjC hqY+v1GMYQa83bsXdhg9WLD7IKZk9kQ8tZW4Pagh9LUYMbHaADMp2kO2QJDDopBCWArvzTwG YKqjAj8cPe7PFQi5mvBeSD1n1gJYCW8RuvvjSjqt5NskK+JIk9tNEjYUknk/Vo4Kj4yqBjec hjAMMxgR4ZGUyE4UCoSLaOArCHXHyAaUdzZhy7HKQAQQ7uB1Ql1IRWeOADMJUwMZi4GJcbhG NiO6QUJWdARORFsxJzkB96MTbjFaMV4mJ+CmGMC/YhViJJDV+KTejjpnQ6CCk5DPz8E5FYmP qIpWn0sEiCesaizMeEO6xmMv0mKjcLXHhJOk4FiXhIlEhuR6KNmAk/4Vpl5u4YZuMTtuA76L MiG/vDqQFcgkrCVUnGME6AxvpfR6tqYi4Ck9Wx/WyH9vJiT7FJ4SG40R8Z3Rx2xEJBFBdDrs cSMnvwiv9UrFzdVhICOAWor23S2qXF9GUGr4SeCxMYQ7CfPOMQIIIxdJGMboy2TwfSdBkMKz iQASE0A5HJmWhEWmSKQ6yI9z5GYiRa+PNqHa4cKjuw/gm949MMliwQU1EmJlr6UQxtyO4Ahh p+tlUQbR2WpBZV19ICtwHWckv5ZYIIvwCQfbW8+GBxLaG8RQFHFnVCS6U5pXTkSuFJDFXyDN 7kFql2hlyEd5R3Dn7jzcai/DgxYHVtoa8LXNAzvRqbNkUOoBgUSQJc4FdLVFonHzUHfMb3iy fi0i86LrdIbuJyzQGkLXQBZgVKPDl5SlJktNF6Wo9CXTil3YLV7ZwfnpxEmlb15JGaEc77Pl S+sai98nxGBajdewePysbHH2CCWa1nojVp/fGwcMHnxaWYvth0u8T0H3l+VTY8cQ1v/Kgm/5 DN3ncnY/DwayAMPUDWur6xQnFqZZkTXUOpxitpy4eEzN7IH46E68an07veTYjlfg+T0F2ESh ZKQkBfQ7XxrcuCrGhotrDJhWZcQqQxTm989QSs1y0+m5sB0mQqS4afC/+yjOpxJ68mqRgryu qJekEHqw32+LhPO9U/k4GKstKqbpHLcZgyCbJ9DF0tV9NxYUYYnVhWiaA2MzEsjoQi77r3UW vJqYhAcuSMOg7olKgUidNXxWX6/sB/oTcZ1xDQbcUG1QXE0FQbwlckdVGOb166ntnt6KyRV7 CdsI3xAe4Lbp8L6HUKBq80kGvHsQewg/Eg7wX2FxrmghQP07vLukeYy9hGeYQA1BBIpC/kbI JxwShpWP/+JHqV24/w8cRO4XhpQ/36jp+yq8L99M57RUFPe28/Nuhup9DGNj9N9IghV7C+DM TMNDdSalvGtXWSyR7gkk1EuYUW/C1LAo7O1rw9eSG7tr61F4sgYbj5RgfUYqLqmWUKtj7QSt kh3eCmFjeigTESRcU2XAe0Sqbxt3DsWE2hTetCyCPUP4+HtW+FLNilVXG1dxVK5V7qUMsRn2 lOa8WO0fEC7QtKeyqf1tECtZBFMb+Xn/QdjJtY874N197U+4TTPmeq7VLCPkEo6z9ZnJRTNh 3V7ivpsIBwmjOcXfwHUJk6JCwKHWRTl/6WbGYUx6MuaarcggZVX5ifANyj4AlJKvIMYJolSx xVsniHXCbxzgN4mmIPJ+k10JNHmhCOMwgLAviOGP8MoEr+TOaPr20WLCXHjfcfiCEMHt27gK Km54Lbyvuan96HqVq8hVkQw8sYJsZn5Os+aZ3lKlgWP4vj/xiryJFaKWhfBuj4sMaJ2qPZLr Nid1vve7HMuJV/PKNPMxn4lywp8L8Gulviz4GdNKS/CKza1QJ0onwvcoW8GyYsbFS4CUECCz VkJcG5Qvri1SxGK7s61xknqbsQ8rP4/N6q1cWBLyuEr5Yvcxm833Up5IdQVSHUBN1yhfuJrB PP5CdhulQQR/NVx1der0WcKr+/ZmnlNf+eDnFot4hG4JN0BMY2jJVR2tqMJju/NxU20pPjQ6 leAuCvqpnkep+3u3iNtSIIqia28nQ7azqLitBNA+1H5W6LPsF78lXEwYqyLMHI0iGjRuYwSv ICFTVO1VbKYPqNo2sklu6flyCLV++lTxdbKCCPB8soeLrP3aUgiq03cBjaQddXE2si+5DG99 9jHWFhXgptgYjCL/Hk00qOMS8C8VUXGsCJPxAhFObpqHikpRZRsvu1RnRY5WHRezP75ItRic 7Dpc7DNt7Ks9mgn+mAmmlS/4eTsHeK69LTy38N+/42cr85N99OIgNpH1Fwb/73cEJMDPzQNB VVTVowfeeP0NJKWk4JH5czF6zFj8efMm9I2LxlWJXTDOHYY0B1kEyVvhc6F1pl/EDp0IB8Jl LHBUY0fz18aOo20bK+IiO3Ta1UoUqeHXQVwrjoloUrV966evK0DaJem4Kj2pZmVqLXQSW6zr mRzCiqj3StxtIUBBoFzbaDQiIsIb1IZbLHjh2SW4d8YMJCalYMkHH+Jf4WEYmtIN2VYLhjgl pDi8LkJxCZL37SC3qt4nvpWJTL14RVQUmA5RwPi+qQHvFB1HSaXu5lBBkBmAXsFRz8ya23At u0b5CGDC2+Kq9M5rJ0JkJf9hcjxB+JQtWBUTtLQVLqMJAUQgc0OzWTKb4XQ6kX/wIOY9/DBe XLFSaR86bDg2bd4Mk8mMh2fPxpNPP43P848oUVNMpwhlx7CnNRxpZiOSKWiMoa8RTuvBSiwQ pWKKD2lJe1DocWM/BXt7jlagrNqOxheFm8kvqZnrxTj1qmORT/+JeSkFuMb/ONhTS7czWDlM 4gB2F6eZ9vasLGZZwsPdVqtVjo6Ols/L7CfPuOceeduWb+TVL+fIUVFRimZWrVwp68mcWbNk rh5rXgH3QrTTDMpG7iOd6mMI9Lq4GuNa8V1mq8YJX56p02e+qs8JntxgpAevet9Yf64ji02x r9+bqnNjue2SFu41n4nqq+HP5HFD/PSPZYs3Tyctrg+4F7Ds+ed39h84YKfZZB4cabMhPSMD 4RHeDGnIsAtRXV2F+2fNwrS77kJMbCwmTp7c5ALCAmRnZyMnJwclx0oR2SkSyUlJGDRoIOrs DuTm5mLAgAHontoDX36xATZbJBK6xmPxkiXBTHp+kD66NSKM1WO84uPYnN4WxDhf7j5KlR3c zhG9Wh5qObtqtfTiVX/Iz/kEtmLa2MPN7f5dg9h0ITwgB5BtW7bIr69ZIxcfPSq3h9w3fXqw vyB6opUTFYwFAPtS9X1yuZzan+sHw7lusKJpqVwp3KjHOTjFFGZ5MmcG2u/w73awAIt5nL80 bzmfn6tpv4Pb+7ZEgHhCkdxOcqiwUP7808+U4x/37ZP3/bC3yfmLR44MRvllHKWL6tkfdIKw X0KAJK7eae/ZwOPUbddpxr7ZwnOXsqXwfX63HQiQzeNe0fQTcyJ+v3GM3dMzmvNDedx8Tbuw CpMIV/lMlbjAc+1lr15esQLjrrwCg7MGYfI1k/Hdzp2NERgFlpWVQaX1/+TNjgmEiVxrDyao DSbSPsqxxWto+mvlMB2iaf2nMPur/VxXkPYW3is4Vd9qYxagruB9xSXuKVzizuES8xG2Spdz yqt9oddX4l7E+wHvsrUQtYPxhCsl1b67qHP/VyfabbWcrKjA3r17sHz5cmSkZ2DhosafGZAr wc1TvAU1CjwxsH9/9OndW4kbjCYjTp6swv4f9x8sKCwclncgv4yebxwXYz5Ayz8tH8JFHRf7 v3Vo+Z1CYSUuYzMZzRaghPcetnKlTy+/HsFmP4nP72BzX8yB4EhefcJvf8hjknkT6h0mIQIE kkIPazQ1gzFMgniOCTYwiat4oUB1L7Ve72brY+B9jWXstlw+F+DDSIJDPk0iYojMfv1OZQMi FtCTn4uKJr69bh2yBg5ESE6zaAggcN/pIsCE8eMVxQ8dMlh+ZvFif0HlAt+zXDtpUkhBHUAA gafaW/kvLV+mKH/ihAmyy+Xy1+1F9XOECNBxBBB4sr2Uv23rVjmpWzf5srFj5Mrycn/dlmuf IUSAjiWAwIz2iAm+ys2V31671t/KdxPm690/RICOJ4DAcMKu0xQW5BEu9XfvEAFOvwRTstzC lbFZnB61h4jUbAGnbRtCaji7CQDORUXx/jx4//+AbWj93rPIifdwuVKUNBdy/hqSDpTW7h+X cxFBvErd0v8TWMdl0YMI/T+BZ638X4ABALiJt5GyzHDtAAAAAElFTkSuQmCC --------------050901040307010200050409-- --------------020604030100000408050001--

2 2

[Engine-devel] Join us in a deep dive into the oVirt-Neutron integration
by Mike Kolesnik 02 Aug '13

02 Aug '13

------=_Part_9764968_1867422127.1375349256826 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Thanks to everyone who participated, I hope the session was enlightening. If you didn't participate, don't miss out... The session recording is available at: https://sas.elluminate.com/p.jnlp?psid=2013-07-31.0603.M.EE511E1083BCFC4B7C… (starts at 3rd minute) Regards, Mike ----- Original Message ----- > The following is a new meeting request: > Subject: Join us in a deep dive into the oVirt-Neutron integration > Organizer: "Mike Kolesnik" <mkolesni(a)redhat.com> Time: Wednesday, July 31, > 2013, 4:00:00 PM - 5:00:00 PM GMT +02:00 Jerusalem Invitees: > users(a)ovirt.org; engine-devel(a)ovirt.org > *~*~*~*~*~*~*~*~*~* > Hi everyone, > As you may know, In oVirt 3.3 we're releasing an integration of OpenStack > Networking service > (a.k.a. Neutron) as another way to define & use VM networks, besides the good > old Linux > Bridge support in VDSM. > You're all invited to join us in a deep dive into this integration, > highlighting the way it works, > the value it brings and how it can be further extended. > The session will take place on Wednesday, Jul 31 , 2013 from 4:00 PM to 5:00 > PM GMT +02:00 (Jerusalem) > The session will be done via Elluminate: > https://sas.elluminate.com/m.jnlp?sid=819&password=M.DF0344C0EEC820394D37F8… > There will also be a teleconferencing bridge available via Intercall: > Bridge id: 972506565679 > Phone numbers: http://www.ovirt.org/Intercall > Regards, > Mike & Livnat ------=_Part_9764968_1867422127.1375349256826 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html><body><div style=3D"font-family: times new roman, new york, times, se= rif; font-size: 12pt; color: #000000"><div>Thanks to everyone who participa= ted, I hope the session was enlightening.<br></div><div><br></div><div>If y= ou didn't participate, don't miss out...</div><div>The session recording is= available at:<br></div><div><a href=3D"https://sas.elluminate.com/p.jnlp?p= sid=3D2013-07-31.0603.M.EE511E1083BCFC4B7C7A2454800447.vcr&sid=3D819">h= ttps://sas.elluminate.com/p.jnlp?psid=3D2013-07-31.0603.M.EE511E1083BCFC4B7= C7A2454800447.vcr&sid=3D819</a></div><div>(starts at 3rd minute)<br></d= iv><div><br></div><div><span name=3D"x"></span>Regards,<br>Mike<span name= =3D"x"></span><br></div><div><br></div><hr id=3D"zwchr"><blockquote style= =3D"border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#0= 00;font-weight:normal;font-style:normal;text-decoration:none;font-family:He= lvetica,Arial,sans-serif;font-size:12pt;" data-mce-style=3D"border-left: 2p= x solid #1010FF; margin-left: 5px; padding-left: 5px; color: #000; font-wei= ght: normal; font-style: normal; text-decoration: none; font-family: Helvet= ica,Arial,sans-serif; font-size: 12pt;"><h3>The following is a new meeting = request:</h3><table class=3D"mceItemTable" border=3D"0"><tbody><tr><th alig= n=3D"left">Subject:</th><td>Join us in a deep dive into the oVirt-Neutron i= ntegration</td></tr><tr><th align=3D"left">Organizer:</th><td>"Mike Kolesni= k" <mkolesni(a)redhat.com></td></tr></tbody></table><table class=3D"mce= ItemTable" border=3D"0"><tbody><tr><th align=3D"left">Time:</th><td>Wednesd= ay, July 31, 2013, 4:00:00 PM - 5:00:00 PM GMT +02:00 Jerusalem</td></tr></= tbody></table><table class=3D"mceItemTable" border=3D"0"><tbody><tr><th ali= gn=3D"left">Invitees:</th><td>users(a)ovirt.org; engine-devel(a)ovirt.org</td><= /tr></tbody></table><div>*~*~*~*~*~*~*~*~*~*</div><p><br></p><div style=3D"= font-family: times new roman, new york, times, serif; font-size: 12pt; colo= r: #000000" data-mce-style=3D"font-family: times new roman, new york, times= , serif; font-size: 12pt; color: #000000;"><div><div>Hi everyone,</div><div= ><br></div><div>As you may know, In oVirt 3.3 we're releasing an integratio= n of OpenStack Networking service</div><div>(a.k.a. Neutron) as another way= to define & use VM networks, besides the good old Linux</div><div>Brid= ge support in VDSM.</div><div><br></div><div>You're all invited to join us = in a deep dive into this integration, highlighting the way it works,</div><= div>the value it brings and how it can be further extended.</div><div><br><= /div><div>The session will take place on Wednesday, <span class=3D"Object" = id=3D"OBJ_PREFIX_DWT856_com_zimbra_date">Jul 31</span>, 2013 from 4:00 PM t= o 5:00 PM GMT +02:00 (Jerusalem)</div><div><br></div><div>The session will = be done via Elluminate:</div><div><a href=3D"https://sas.elluminate.com/m.j= nlp?sid=3D819&password=3DM.DF0344C0EEC820394D37F89D9BE68C" target=3D"_b= lank" data-mce-href=3D"https://sas.elluminate.com/m.jnlp?sid=3D819&pass= word=3DM.DF0344C0EEC820394D37F89D9BE68C">https://sas.elluminate.com/m.jnlp?= sid=3D819&password=3DM.DF0344C0EEC820394D37F89D9BE68C</a><br></div><div= ><br></div><div>There will also be a teleconferencing bridge available via = Intercall:</div><div>Bridge id: 972506565679</div><div>Phone numbers: http:= //www.ovirt.org/Intercall</div><div><br></div><span></span>Regards,<br>Mike= & Livnat<span></span></div></div></blockquote><div><br></div></div></b= ody></html> ------=_Part_9764968_1867422127.1375349256826--

3 2

[Engine-devel] [oVirt 3.3 Localization Question #3 and #4]
by Yuko Katabami 01 Aug '13

01 Aug '13

This is a multi-part message in MIME format. --------------030903000403050902070203 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hello, I would like to ask a couple more questions for translation: #3 *File: *LocalizedEnums *Resource IDs: * AuditLogType___IMPORTEXPORT_IMPORT_VM_FROM_TRUSTED_TO_UNTRUSTED AuditLogType___IMPORTEXPORT_IMPORT_VM_FROM_UNTRUSTED_TO_TRUSTED *Strings:* Import VM from trusted cluster into non-trusted cluster Import VM from non-trusted cluster into trusted cluster *Question: *Since these strings are audit logs, should "Import" be "Imported", stating the past event? #4 *File: *AppErrors *Resource ID: *VAR__ACTION__SCAN_ALIGNMENT *String:* $action scan alignment *Question: *"Alignment" can be translated in a few different ways depending on the context. Could anyone tell me how this action is used? Is it referring disk partition alignment? It would be very much appreciated if anyone who knows the answer could help me with those questions. Thank you. Yuko -- Regards, Yuko Katabami (?????) Technical Translator II NAATI Accredited Professional Translator (English into Japanese) #28138 RHCSA #111-119-244 *Mobile:* +61 415 847 352 *Email:* ykatabam(a)redhat.com Red Hat *Red Hat, Asia-Pacific Pty Ltd* Level 1, 193 North Quay Brisbane 4000 *Office:* +61 7 3514 8100 *Fax:* +61 7 3514 8199 *Website:* www.redhat.com <http://www.redhat.com> *Facebook:* Red Hat APAC <http://www.facebook.com/redhatapac> | Red Hat Japan <http://www.facebook.com/redhatjapan> | Red Hat Korea <http://www.facebook.com/redhatkorea> | JBoss APAC <http://www.facebook.com/JBossAPAC> *Twitter:* Red Hat APAC <http://www.twitter.com/red_hat_apac> | Red Hat ANZ <http://www.twitter.com/redhatanz> *LinkedIn:* Red Hat APAC <http://www.linkedin.com/groups?gid=3124596> | JBoss APAC <http://www.linkedin.com/groups?gid=4068303> --------------030903000403050902070203 Content-Type: multipart/related; boundary="------------070803020305010504020203" --------------070803020305010504020203 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"> Hello,<br> <br> I would like to ask a couple more questions for translation:<br> <br> #3<br> <b>File: </b>LocalizedEnums<br> <b>Resource IDs: </b><br> AuditLogType___IMPORTEXPORT_IMPORT_VM_FROM_TRUSTED_TO_UNTRUSTED<br> AuditLogType___IMPORTEXPORT_IMPORT_VM_FROM_UNTRUSTED_TO_TRUSTED<br> <b>Strings:</b><br> Import VM from trusted cluster into non-trusted cluster<br> Import VM from non-trusted cluster into trusted cluster<br> <b>Question: </b>Since these strings are audit logs, should "Import" be "Imported", stating the past event?<br> <br> #4<br> <b>File: </b>AppErrors<br> <b>Resource ID: </b>VAR__ACTION__SCAN_ALIGNMENT<br> <b>String:</b> $action scan alignment<br> <b>Question: </b>"Alignment" can be translated in a few different ways depending on the context. Could anyone tell me how this action is used? Is it referring disk partition alignment?<br> <br> It would be very much appreciated if anyone who knows the answer could help me with those questions.<br> <br> Thank you.<br> <br> Yuko<br> <div class="moz-signature">-- <br> <font color="#000000" face="arial, sans-serif" size="2"> Regards, <br> <br> Yuko Katabami (方波見裕子) <br> Technical Translator II <br> NAATI Accredited Professional Translator (English into Japanese) #28138 <br> RHCSA #111-119-244 <br> <b>Mobile:</b> +61 415 847 352 <br> <b>Email:</b> <a class="moz-txt-link-abbreviated" href="mailto:ykatabam@redhat.com">ykatabam(a)redhat.com</a> <br> <br> <a target="_blank"><img src="cid:part1.00010909.03050606@redhat.com" alt="Red Hat" height="42" border="0" width="128"></a> <br> <br> <b>Red Hat, Asia-Pacific Pty Ltd</b> <br> Level 1, 193 North Quay <br> Brisbane 4000 <br> <b>Office:</b> +61 7 3514 8100 <br> <b>Fax:</b> +61 7 3514 8199 <br> <b>Website:</b> <a href="http://www.redhat.com" target="_blank">www.redhat.com</a> <br> <br> <b>Facebook:</b> <a href="http://www.facebook.com/redhatapac" target="_blank">Red Hat APAC</a> | <a href="http://www.facebook.com/redhatjapan" target="_blank">Red Hat Japan</a> | <a href="http://www.facebook.com/redhatkorea" target="_blank">Red Hat Korea</a> | <a href="http://www.facebook.com/JBossAPAC" target="_blank">JBoss APAC</a> <br> <b>Twitter:</b> <a href="http://www.twitter.com/red_hat_apac" target="_blank">Red Hat APAC</a> | <a href="http://www.twitter.com/redhatanz" target="_blank">Red Hat ANZ</a> <br> <b>LinkedIn:</b> <a href="http://www.linkedin.com/groups?gid=3124596" target="_blank">Red Hat APAC</a> | <a href="http://www.linkedin.com/groups?gid=4068303" target="_blank">JBoss APAC</a> </font> </div> </body> </html> --------------070803020305010504020203 Content-Type: image/png; name="redhat-logo.png" Content-Transfer-Encoding: base64 Content-ID: <part1.00010909.03050606(a)redhat.com> Content-Disposition: inline; filename="redhat-logo.png" iVBORw0KGgoAAAANSUhEUgAAAIAAAAApCAYAAAD9LSHtAAAAGXRFWHRTb2Z0d2FyZQBBZG9i ZSBJbWFnZVJlYWR5ccllPAAAA6NpVFh0WE1MOmNvbS5hZG9iZS54bXAAAAAAADw/eHBhY2tl dCBiZWdpbj0i77u/IiBpZD0iVzVNME1wQ2VoaUh6cmVTek5UY3prYzlkIj8+IDx4OnhtcG1l dGEgeG1sbnM6eD0iYWRvYmU6bnM6bWV0YS8iIHg6eG1wdGs9IkFkb2JlIFhNUCBDb3JlIDUu MC1jMDYxIDY0LjE0MDk0OSwgMjAxMC8xMi8wNy0xMDo1NzowMSAgICAgICAgIj4gPHJkZjpS REYgeG1sbnM6cmRmPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5LzAyLzIyLXJkZi1zeW50YXgt bnMjIj4gPHJkZjpEZXNjcmlwdGlvbiByZGY6YWJvdXQ9IiIgeG1sbnM6eG1wTU09Imh0dHA6 Ly9ucy5hZG9iZS5jb20veGFwLzEuMC9tbS8iIHhtbG5zOnN0UmVmPSJodHRwOi8vbnMuYWRv YmUuY29tL3hhcC8xLjAvc1R5cGUvUmVzb3VyY2VSZWYjIiB4bWxuczp4bXA9Imh0dHA6Ly9u cy5hZG9iZS5jb20veGFwLzEuMC8iIHhtbG5zOmRjPSJodHRwOi8vcHVybC5vcmcvZGMvZWxl bWVudHMvMS4xLyIgeG1wTU06RG9jdW1lbnRJRD0ieG1wLmRpZDpDMTM3NDQ3MkZCQzExMUUw OTQzNzk0QTNCNkFFNjg1RCIgeG1wTU06SW5zdGFuY2VJRD0ieG1wLmlpZDpDMTM3NDQ3MUZC QzExMUUwOTQzNzk0QTNCNkFFNjg1RCIgeG1wOkNyZWF0b3JUb29sPSJBZG9iZSBJbGx1c3Ry YXRvciBDUzMiPiA8eG1wTU06RGVyaXZlZEZyb20gc3RSZWY6aW5zdGFuY2VJRD0idXVpZDpD QzZBQjQzODY4MDNERDExOENBRDk2OTlCQTZCNjM4OSIgc3RSZWY6ZG9jdW1lbnRJRD0idXVp ZDpDQjZBQjQzODY4MDNERDExOENBRDk2OTlCQTZCNjM4OSIvPiA8ZGM6dGl0bGU+IDxyZGY6 QWx0PiA8cmRmOmxpIHhtbDpsYW5nPSJ4LWRlZmF1bHQiPnJlZGhhdF9jbXlrX2xvZ288L3Jk ZjpsaT4gPC9yZGY6QWx0PiA8L2RjOnRpdGxlPiA8L3JkZjpEZXNjcmlwdGlvbj4gPC9yZGY6 UkRGPiA8L3g6eG1wbWV0YT4gPD94cGFja2V0IGVuZD0iciI/Pv93CnUAAA4OSURBVHja7FwL dBTVGf5ms49kySYkgSQkIZCkvKLyCCAIEQRFLdIiqPUN4qsitmhFQKgWKlpRQT1HsEINePBR hfr2+ECUtAoICCggGEKCEEkC5EFeu9nN7vS/s/+SyWR2s4mBgGf/cz4ye+femdn7f/d/3Vkk tE0MhPMJowgXEXoRkgidCDJBItgJxYQCwhbCRsL3BBdCcs5KLGEGYSuhgZUdLDyE3YQ5hITQ VJ5bEk54kFe03A4oJywgRIWm9uyX4YRdzZVo0EBSwffZ11fSfD6FPMKloSnuOJFaOC/M/RKC RT0kMtyM0amJSDYZ4ZJlFLvcOFJrR62rARFGI/pEWTHYYkKiLMFEIwpJ9+9X1GDnkRLWexMR ruFRwuMhdZxdBHiS/XVTX0BKX9o3HVdUS6RK73AXHdUpQYEMM7W5jMCOCBnbPA04aHeid4QF 1zUY8ZzswEd5h/VIIORFwr0hlZxZCfPT/hRhtl7wPy4jBTPtJtTTpypSpIPgIqVLyllJUa2b rEKCE4iwGLD6cDE2HS1D/+RY/NFhwnqzjPJah949hxISCR+F1NKxBLiPsMjfgBtTuiLFKWGX TUZvpwERpPRwholQr1zUS4gCCh37xNpwd3wchpHFsJFLkOMikFta7u/yQ9gqbQyppmNcwEjC hqY+v1GMYQa83bsXdhg9WLD7IKZk9kQ8tZW4Pagh9LUYMbHaADMp2kO2QJDDopBCWArvzTwG YKqjAj8cPe7PFQi5mvBeSD1n1gJYCW8RuvvjSjqt5NskK+JIk9tNEjYUknk/Vo4Kj4yqBjec hjAMMxgR4ZGUyE4UCoSLaOArCHXHyAaUdzZhy7HKQAQQ7uB1Ql1IRWeOADMJUwMZi4GJcbhG NiO6QUJWdARORFsxJzkB96MTbjFaMV4mJ+CmGMC/YhViJJDV+KTejjpnQ6CCk5DPz8E5FYmP qIpWn0sEiCesaizMeEO6xmMv0mKjcLXHhJOk4FiXhIlEhuR6KNmAk/4Vpl5u4YZuMTtuA76L MiG/vDqQFcgkrCVUnGME6AxvpfR6tqYi4Ck9Wx/WyH9vJiT7FJ4SG40R8Z3Rx2xEJBFBdDrs cSMnvwiv9UrFzdVhICOAWor23S2qXF9GUGr4SeCxMYQ7CfPOMQIIIxdJGMboy2TwfSdBkMKz iQASE0A5HJmWhEWmSKQ6yI9z5GYiRa+PNqHa4cKjuw/gm949MMliwQU1EmJlr6UQxtyO4Ahh p+tlUQbR2WpBZV19ICtwHWckv5ZYIIvwCQfbW8+GBxLaG8RQFHFnVCS6U5pXTkSuFJDFXyDN 7kFql2hlyEd5R3Dn7jzcai/DgxYHVtoa8LXNAzvRqbNkUOoBgUSQJc4FdLVFonHzUHfMb3iy fi0i86LrdIbuJyzQGkLXQBZgVKPDl5SlJktNF6Wo9CXTil3YLV7ZwfnpxEmlb15JGaEc77Pl S+sai98nxGBajdewePysbHH2CCWa1nojVp/fGwcMHnxaWYvth0u8T0H3l+VTY8cQ1v/Kgm/5 DN3ncnY/DwayAMPUDWur6xQnFqZZkTXUOpxitpy4eEzN7IH46E68an07veTYjlfg+T0F2ESh ZKQkBfQ7XxrcuCrGhotrDJhWZcQqQxTm989QSs1y0+m5sB0mQqS4afC/+yjOpxJ68mqRgryu qJekEHqw32+LhPO9U/k4GKstKqbpHLcZgyCbJ9DF0tV9NxYUYYnVhWiaA2MzEsjoQi77r3UW vJqYhAcuSMOg7olKgUidNXxWX6/sB/oTcZ1xDQbcUG1QXE0FQbwlckdVGOb166ntnt6KyRV7 CdsI3xAe4Lbp8L6HUKBq80kGvHsQewg/Eg7wX2FxrmghQP07vLukeYy9hGeYQA1BBIpC/kbI JxwShpWP/+JHqV24/w8cRO4XhpQ/36jp+yq8L99M57RUFPe28/Nuhup9DGNj9N9IghV7C+DM TMNDdSalvGtXWSyR7gkk1EuYUW/C1LAo7O1rw9eSG7tr61F4sgYbj5RgfUYqLqmWUKtj7QSt kh3eCmFjeigTESRcU2XAe0Sqbxt3DsWE2hTetCyCPUP4+HtW+FLNilVXG1dxVK5V7qUMsRn2 lOa8WO0fEC7QtKeyqf1tECtZBFMb+Xn/QdjJtY874N197U+4TTPmeq7VLCPkEo6z9ZnJRTNh 3V7ivpsIBwmjOcXfwHUJk6JCwKHWRTl/6WbGYUx6MuaarcggZVX5ifANyj4AlJKvIMYJolSx xVsniHXCbxzgN4mmIPJ+k10JNHmhCOMwgLAviOGP8MoEr+TOaPr20WLCXHjfcfiCEMHt27gK Km54Lbyvuan96HqVq8hVkQw8sYJsZn5Os+aZ3lKlgWP4vj/xiryJFaKWhfBuj4sMaJ2qPZLr Nid1vve7HMuJV/PKNPMxn4lywp8L8Gulviz4GdNKS/CKza1QJ0onwvcoW8GyYsbFS4CUECCz VkJcG5Qvri1SxGK7s61xknqbsQ8rP4/N6q1cWBLyuEr5Yvcxm833Up5IdQVSHUBN1yhfuJrB PP5CdhulQQR/NVx1der0WcKr+/ZmnlNf+eDnFot4hG4JN0BMY2jJVR2tqMJju/NxU20pPjQ6 leAuCvqpnkep+3u3iNtSIIqia28nQ7azqLitBNA+1H5W6LPsF78lXEwYqyLMHI0iGjRuYwSv ICFTVO1VbKYPqNo2sklu6flyCLV++lTxdbKCCPB8soeLrP3aUgiq03cBjaQddXE2si+5DG99 9jHWFhXgptgYjCL/Hk00qOMS8C8VUXGsCJPxAhFObpqHikpRZRsvu1RnRY5WHRezP75ItRic 7Dpc7DNt7Ks9mgn+mAmmlS/4eTsHeK69LTy38N+/42cr85N99OIgNpH1Fwb/73cEJMDPzQNB VVTVowfeeP0NJKWk4JH5czF6zFj8efMm9I2LxlWJXTDOHYY0B1kEyVvhc6F1pl/EDp0IB8Jl LHBUY0fz18aOo20bK+IiO3Ta1UoUqeHXQVwrjoloUrV966evK0DaJem4Kj2pZmVqLXQSW6zr mRzCiqj3StxtIUBBoFzbaDQiIsIb1IZbLHjh2SW4d8YMJCalYMkHH+Jf4WEYmtIN2VYLhjgl pDi8LkJxCZL37SC3qt4nvpWJTL14RVQUmA5RwPi+qQHvFB1HSaXu5lBBkBmAXsFRz8ya23At u0b5CGDC2+Kq9M5rJ0JkJf9hcjxB+JQtWBUTtLQVLqMJAUQgc0OzWTKb4XQ6kX/wIOY9/DBe XLFSaR86bDg2bd4Mk8mMh2fPxpNPP43P848oUVNMpwhlx7CnNRxpZiOSKWiMoa8RTuvBSiwQ pWKKD2lJe1DocWM/BXt7jlagrNqOxheFm8kvqZnrxTj1qmORT/+JeSkFuMb/ONhTS7czWDlM 4gB2F6eZ9vasLGZZwsPdVqtVjo6Ols/L7CfPuOceeduWb+TVL+fIUVFRimZWrVwp68mcWbNk rh5rXgH3QrTTDMpG7iOd6mMI9Lq4GuNa8V1mq8YJX56p02e+qs8JntxgpAevet9Yf64ji02x r9+bqnNjue2SFu41n4nqq+HP5HFD/PSPZYs3Tyctrg+4F7Ds+ed39h84YKfZZB4cabMhPSMD 4RHeDGnIsAtRXV2F+2fNwrS77kJMbCwmTp7c5ALCAmRnZyMnJwclx0oR2SkSyUlJGDRoIOrs DuTm5mLAgAHontoDX36xATZbJBK6xmPxkiXBTHp+kD66NSKM1WO84uPYnN4WxDhf7j5KlR3c zhG9Wh5qObtqtfTiVX/Iz/kEtmLa2MPN7f5dg9h0ITwgB5BtW7bIr69ZIxcfPSq3h9w3fXqw vyB6opUTFYwFAPtS9X1yuZzan+sHw7lusKJpqVwp3KjHOTjFFGZ5MmcG2u/w73awAIt5nL80 bzmfn6tpv4Pb+7ZEgHhCkdxOcqiwUP7808+U4x/37ZP3/bC3yfmLR44MRvllHKWL6tkfdIKw X0KAJK7eae/ZwOPUbddpxr7ZwnOXsqXwfX63HQiQzeNe0fQTcyJ+v3GM3dMzmvNDedx8Tbuw CpMIV/lMlbjAc+1lr15esQLjrrwCg7MGYfI1k/Hdzp2NERgFlpWVQaX1/+TNjgmEiVxrDyao DSbSPsqxxWto+mvlMB2iaf2nMPur/VxXkPYW3is4Vd9qYxagruB9xSXuKVzizuES8xG2Spdz yqt9oddX4l7E+wHvsrUQtYPxhCsl1b67qHP/VyfabbWcrKjA3r17sHz5cmSkZ2DhosafGZAr wc1TvAU1CjwxsH9/9OndW4kbjCYjTp6swv4f9x8sKCwclncgv4yebxwXYz5Ayz8tH8JFHRf7 v3Vo+Z1CYSUuYzMZzRaghPcetnKlTy+/HsFmP4nP72BzX8yB4EhefcJvf8hjknkT6h0mIQIE kkIPazQ1gzFMgniOCTYwiat4oUB1L7Ve72brY+B9jWXstlw+F+DDSIJDPk0iYojMfv1OZQMi FtCTn4uKJr69bh2yBg5ESE6zaAggcN/pIsCE8eMVxQ8dMlh+ZvFif0HlAt+zXDtpUkhBHUAA gafaW/kvLV+mKH/ihAmyy+Xy1+1F9XOECNBxBBB4sr2Uv23rVjmpWzf5srFj5Mrycn/dlmuf IUSAjiWAwIz2iAm+ys2V31671t/KdxPm690/RICOJ4DAcMKu0xQW5BEu9XfvEAFOvwRTstzC lbFZnB61h4jUbAGnbRtCaji7CQDORUXx/jx4//+AbWj93rPIifdwuVKUNBdy/hqSDpTW7h+X cxFBvErd0v8TWMdl0YMI/T+BZ638X4ABALiJt5GyzHDtAAAAAElFTkSuQmCC --------------070803020305010504020203-- --------------030903000403050902070203--

2 2

[Engine-devel] [oVirt jenkins] Weekly report on open tasks for ovirt-engine
by Jenkins ci oVirt Server 01 Aug '13

01 Aug '13

------=_Part_40_614977538.1375311778010 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit <b>Files scanned: '**/*.java, **/*.py'. </b><br> <b>Strings searched: FIXME | TODO | @deprecated </b> <br><br> Report: http://jenkins.ovirt.org/job/ovirt_engine_scan_open_tasks/10/tasksResult/? ------=_Part_40_614977538.1375311778010--

2 1

[Engine-devel] ovirt-engine-3.3 branch created
by Ofer Schreiber 31 Jul '13

31 Jul '13

Hey, I have just created the ovirt-engine-3.3 branch in gerrit.ovirt.org, which will be used for 3.3 builds. Please make sure you cherry pick important patches (== blockers) into that branch, otherwise, 3.3 will miss them. If you are unsure if a patch should get inside 3.3 branch, please feel free to contact me. Regards, -- Ofer Schreiber

1 0

[Engine-devel] [oVirt/RHEV 3.3 Localization Question #2] gluster hook stage "Pre" and "Post"
by Yuko Katabami 31 Jul '13

31 Jul '13

This is a multi-part message in MIME format. --------------020707080904020408090704 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hello all, I am a Brisbane-based translator currently working on the oVirt/RHEV 3.3 localization project along with 5 other translators. I was suggested to post my localization-related questions to this mailing list instead of rhev-devel. We often have difficulty in comprehending some strings or are unable to determine the usage of strings without knowing the context. In order to translate software UI strings accurately, we need extra information from time to time. It would be very much appreciated if any of you can help us by responding my email. My question this time is about the following strings: File: LocalizedEnums Resource Ids: "GlusterHookStage___PRE" and "GlusterHookStage___POST" Strings: "Pre" and "Post" Question: Could anyone explain how these are used? In our language we need to know what comes after "Pre" and "Post", otherwise our translation would become "Front" and "Back" that would not make sense in this case. Thank you. Kind regards, Yuko -- Regards, Yuko Katabami (?????) Technical Translator II NAATI Accredited Professional Translator (English into Japanese) #28138 RHCSA #111-119-244 *Mobile:* +61 415 847 352 *Email:* ykatabam(a)redhat.com Red Hat *Red Hat, Asia-Pacific Pty Ltd* Level 1, 193 North Quay Brisbane 4000 *Office:* +61 7 3514 8100 *Fax:* +61 7 3514 8199 *Website:* www.redhat.com <http://www.redhat.com> *Facebook:* Red Hat APAC <http://www.facebook.com/redhatapac> | Red Hat Japan <http://www.facebook.com/redhatjapan> | Red Hat Korea <http://www.facebook.com/redhatkorea> | JBoss APAC <http://www.facebook.com/JBossAPAC> *Twitter:* Red Hat APAC <http://www.twitter.com/red_hat_apac> | Red Hat ANZ <http://www.twitter.com/redhatanz> *LinkedIn:* Red Hat APAC <http://www.linkedin.com/groups?gid=3124596> | JBoss APAC <http://www.linkedin.com/groups?gid=4068303> --------------020707080904020408090704 Content-Type: multipart/related; boundary="------------070206040803090007060302" --------------070206040803090007060302 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"> Hello all,<br> <br> I am a Brisbane-based translator currently working on the oVirt/RHEV 3.3 localization project along with 5 other translators.<br> I was suggested to post my localization-related questions to this mailing list instead of rhev-devel.<br> <br> We often have difficulty in comprehending some strings or are unable to determine the usage of strings without knowing the context. <br> In order to translate software UI strings accurately, we need extra information from time to time.<br> It would be very much appreciated if any of you can help us by responding my email.<br> <br> My question this time is about the following strings:<br> File: LocalizedEnums<br> Resource Ids: "GlusterHookStage___PRE" and "GlusterHookStage___POST"<br> Strings: "Pre" and "Post"<br> Question: Could anyone explain how these are used? In our language we need to know what comes after "Pre" and "Post", otherwise our translation would become "Front" and "Back" that would not make sense in this case.<br> <br> Thank you.<br> <br> Kind regards,<br> <br> Yuko<br> <br> <br> <div class="moz-signature">-- <br> <font color="#000000" face="arial, sans-serif" size="2"> Regards, <br> <br> Yuko Katabami (方波見裕子) <br> Technical Translator II <br> NAATI Accredited Professional Translator (English into Japanese) #28138 <br> RHCSA #111-119-244 <br> <b>Mobile:</b> +61 415 847 352 <br> <b>Email:</b> <a class="moz-txt-link-abbreviated" href="mailto:ykatabam@redhat.com">ykatabam(a)redhat.com</a> <br> <br> <a target="_blank"><img src="cid:part1.01040103.07010606@redhat.com" alt="Red Hat" height="42" border="0" width="128"></a> <br> <br> <b>Red Hat, Asia-Pacific Pty Ltd</b> <br> Level 1, 193 North Quay <br> Brisbane 4000 <br> <b>Office:</b> +61 7 3514 8100 <br> <b>Fax:</b> +61 7 3514 8199 <br> <b>Website:</b> <a href="http://www.redhat.com" target="_blank">www.redhat.com</a> <br> <br> <b>Facebook:</b> <a href="http://www.facebook.com/redhatapac" target="_blank">Red Hat APAC</a> | <a href="http://www.facebook.com/redhatjapan" target="_blank">Red Hat Japan</a> | <a href="http://www.facebook.com/redhatkorea" target="_blank">Red Hat Korea</a> | <a href="http://www.facebook.com/JBossAPAC" target="_blank">JBoss APAC</a> <br> <b>Twitter:</b> <a href="http://www.twitter.com/red_hat_apac" target="_blank">Red Hat APAC</a> | <a href="http://www.twitter.com/redhatanz" target="_blank">Red Hat ANZ</a> <br> <b>LinkedIn:</b> <a href="http://www.linkedin.com/groups?gid=3124596" target="_blank">Red Hat APAC</a> | <a href="http://www.linkedin.com/groups?gid=4068303" target="_blank">JBoss APAC</a> </font> </div> </body> </html> --------------070206040803090007060302 Content-Type: image/png; name="redhat-logo.png" Content-Transfer-Encoding: base64 Content-ID: <part1.01040103.07010606(a)redhat.com> Content-Disposition: inline; filename="redhat-logo.png" iVBORw0KGgoAAAANSUhEUgAAAIAAAAApCAYAAAD9LSHtAAAAGXRFWHRTb2Z0d2FyZQBBZG9i ZSBJbWFnZVJlYWR5ccllPAAAA6NpVFh0WE1MOmNvbS5hZG9iZS54bXAAAAAAADw/eHBhY2tl dCBiZWdpbj0i77u/IiBpZD0iVzVNME1wQ2VoaUh6cmVTek5UY3prYzlkIj8+IDx4OnhtcG1l dGEgeG1sbnM6eD0iYWRvYmU6bnM6bWV0YS8iIHg6eG1wdGs9IkFkb2JlIFhNUCBDb3JlIDUu MC1jMDYxIDY0LjE0MDk0OSwgMjAxMC8xMi8wNy0xMDo1NzowMSAgICAgICAgIj4gPHJkZjpS REYgeG1sbnM6cmRmPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5LzAyLzIyLXJkZi1zeW50YXgt bnMjIj4gPHJkZjpEZXNjcmlwdGlvbiByZGY6YWJvdXQ9IiIgeG1sbnM6eG1wTU09Imh0dHA6 Ly9ucy5hZG9iZS5jb20veGFwLzEuMC9tbS8iIHhtbG5zOnN0UmVmPSJodHRwOi8vbnMuYWRv YmUuY29tL3hhcC8xLjAvc1R5cGUvUmVzb3VyY2VSZWYjIiB4bWxuczp4bXA9Imh0dHA6Ly9u cy5hZG9iZS5jb20veGFwLzEuMC8iIHhtbG5zOmRjPSJodHRwOi8vcHVybC5vcmcvZGMvZWxl bWVudHMvMS4xLyIgeG1wTU06RG9jdW1lbnRJRD0ieG1wLmRpZDpDMTM3NDQ3MkZCQzExMUUw OTQzNzk0QTNCNkFFNjg1RCIgeG1wTU06SW5zdGFuY2VJRD0ieG1wLmlpZDpDMTM3NDQ3MUZC QzExMUUwOTQzNzk0QTNCNkFFNjg1RCIgeG1wOkNyZWF0b3JUb29sPSJBZG9iZSBJbGx1c3Ry YXRvciBDUzMiPiA8eG1wTU06RGVyaXZlZEZyb20gc3RSZWY6aW5zdGFuY2VJRD0idXVpZDpD QzZBQjQzODY4MDNERDExOENBRDk2OTlCQTZCNjM4OSIgc3RSZWY6ZG9jdW1lbnRJRD0idXVp ZDpDQjZBQjQzODY4MDNERDExOENBRDk2OTlCQTZCNjM4OSIvPiA8ZGM6dGl0bGU+IDxyZGY6 QWx0PiA8cmRmOmxpIHhtbDpsYW5nPSJ4LWRlZmF1bHQiPnJlZGhhdF9jbXlrX2xvZ288L3Jk ZjpsaT4gPC9yZGY6QWx0PiA8L2RjOnRpdGxlPiA8L3JkZjpEZXNjcmlwdGlvbj4gPC9yZGY6 UkRGPiA8L3g6eG1wbWV0YT4gPD94cGFja2V0IGVuZD0iciI/Pv93CnUAAA4OSURBVHja7FwL dBTVGf5ms49kySYkgSQkIZCkvKLyCCAIEQRFLdIiqPUN4qsitmhFQKgWKlpRQT1HsEINePBR hfr2+ECUtAoICCggGEKCEEkC5EFeu9nN7vS/s/+SyWR2s4mBgGf/cz4ye+femdn7f/d/3Vkk tE0MhPMJowgXEXoRkgidCDJBItgJxYQCwhbCRsL3BBdCcs5KLGEGYSuhgZUdLDyE3YQ5hITQ VJ5bEk54kFe03A4oJywgRIWm9uyX4YRdzZVo0EBSwffZ11fSfD6FPMKloSnuOJFaOC/M/RKC RT0kMtyM0amJSDYZ4ZJlFLvcOFJrR62rARFGI/pEWTHYYkKiLMFEIwpJ9+9X1GDnkRLWexMR ruFRwuMhdZxdBHiS/XVTX0BKX9o3HVdUS6RK73AXHdUpQYEMM7W5jMCOCBnbPA04aHeid4QF 1zUY8ZzswEd5h/VIIORFwr0hlZxZCfPT/hRhtl7wPy4jBTPtJtTTpypSpIPgIqVLyllJUa2b rEKCE4iwGLD6cDE2HS1D/+RY/NFhwnqzjPJah949hxISCR+F1NKxBLiPsMjfgBtTuiLFKWGX TUZvpwERpPRwholQr1zUS4gCCh37xNpwd3wchpHFsJFLkOMikFta7u/yQ9gqbQyppmNcwEjC hqY+v1GMYQa83bsXdhg9WLD7IKZk9kQ8tZW4Pagh9LUYMbHaADMp2kO2QJDDopBCWArvzTwG YKqjAj8cPe7PFQi5mvBeSD1n1gJYCW8RuvvjSjqt5NskK+JIk9tNEjYUknk/Vo4Kj4yqBjec hjAMMxgR4ZGUyE4UCoSLaOArCHXHyAaUdzZhy7HKQAQQ7uB1Ql1IRWeOADMJUwMZi4GJcbhG NiO6QUJWdARORFsxJzkB96MTbjFaMV4mJ+CmGMC/YhViJJDV+KTejjpnQ6CCk5DPz8E5FYmP qIpWn0sEiCesaizMeEO6xmMv0mKjcLXHhJOk4FiXhIlEhuR6KNmAk/4Vpl5u4YZuMTtuA76L MiG/vDqQFcgkrCVUnGME6AxvpfR6tqYi4Ck9Wx/WyH9vJiT7FJ4SG40R8Z3Rx2xEJBFBdDrs cSMnvwiv9UrFzdVhICOAWor23S2qXF9GUGr4SeCxMYQ7CfPOMQIIIxdJGMboy2TwfSdBkMKz iQASE0A5HJmWhEWmSKQ6yI9z5GYiRa+PNqHa4cKjuw/gm949MMliwQU1EmJlr6UQxtyO4Ahh p+tlUQbR2WpBZV19ICtwHWckv5ZYIIvwCQfbW8+GBxLaG8RQFHFnVCS6U5pXTkSuFJDFXyDN 7kFql2hlyEd5R3Dn7jzcai/DgxYHVtoa8LXNAzvRqbNkUOoBgUSQJc4FdLVFonHzUHfMb3iy fi0i86LrdIbuJyzQGkLXQBZgVKPDl5SlJktNF6Wo9CXTil3YLV7ZwfnpxEmlb15JGaEc77Pl S+sai98nxGBajdewePysbHH2CCWa1nojVp/fGwcMHnxaWYvth0u8T0H3l+VTY8cQ1v/Kgm/5 DN3ncnY/DwayAMPUDWur6xQnFqZZkTXUOpxitpy4eEzN7IH46E68an07veTYjlfg+T0F2ESh ZKQkBfQ7XxrcuCrGhotrDJhWZcQqQxTm989QSs1y0+m5sB0mQqS4afC/+yjOpxJ68mqRgryu qJekEHqw32+LhPO9U/k4GKstKqbpHLcZgyCbJ9DF0tV9NxYUYYnVhWiaA2MzEsjoQi77r3UW vJqYhAcuSMOg7olKgUidNXxWX6/sB/oTcZ1xDQbcUG1QXE0FQbwlckdVGOb166ntnt6KyRV7 CdsI3xAe4Lbp8L6HUKBq80kGvHsQewg/Eg7wX2FxrmghQP07vLukeYy9hGeYQA1BBIpC/kbI JxwShpWP/+JHqV24/w8cRO4XhpQ/36jp+yq8L99M57RUFPe28/Nuhup9DGNj9N9IghV7C+DM TMNDdSalvGtXWSyR7gkk1EuYUW/C1LAo7O1rw9eSG7tr61F4sgYbj5RgfUYqLqmWUKtj7QSt kh3eCmFjeigTESRcU2XAe0Sqbxt3DsWE2hTetCyCPUP4+HtW+FLNilVXG1dxVK5V7qUMsRn2 lOa8WO0fEC7QtKeyqf1tECtZBFMb+Xn/QdjJtY874N197U+4TTPmeq7VLCPkEo6z9ZnJRTNh 3V7ivpsIBwmjOcXfwHUJk6JCwKHWRTl/6WbGYUx6MuaarcggZVX5ifANyj4AlJKvIMYJolSx xVsniHXCbxzgN4mmIPJ+k10JNHmhCOMwgLAviOGP8MoEr+TOaPr20WLCXHjfcfiCEMHt27gK Km54Lbyvuan96HqVq8hVkQw8sYJsZn5Os+aZ3lKlgWP4vj/xiryJFaKWhfBuj4sMaJ2qPZLr Nid1vve7HMuJV/PKNPMxn4lywp8L8Gulviz4GdNKS/CKza1QJ0onwvcoW8GyYsbFS4CUECCz VkJcG5Qvri1SxGK7s61xknqbsQ8rP4/N6q1cWBLyuEr5Yvcxm833Up5IdQVSHUBN1yhfuJrB PP5CdhulQQR/NVx1der0WcKr+/ZmnlNf+eDnFot4hG4JN0BMY2jJVR2tqMJju/NxU20pPjQ6 leAuCvqpnkep+3u3iNtSIIqia28nQ7azqLitBNA+1H5W6LPsF78lXEwYqyLMHI0iGjRuYwSv ICFTVO1VbKYPqNo2sklu6flyCLV++lTxdbKCCPB8soeLrP3aUgiq03cBjaQddXE2si+5DG99 9jHWFhXgptgYjCL/Hk00qOMS8C8VUXGsCJPxAhFObpqHikpRZRsvu1RnRY5WHRezP75ItRic 7Dpc7DNt7Ks9mgn+mAmmlS/4eTsHeK69LTy38N+/42cr85N99OIgNpH1Fwb/73cEJMDPzQNB VVTVowfeeP0NJKWk4JH5czF6zFj8efMm9I2LxlWJXTDOHYY0B1kEyVvhc6F1pl/EDp0IB8Jl LHBUY0fz18aOo20bK+IiO3Ta1UoUqeHXQVwrjoloUrV966evK0DaJem4Kj2pZmVqLXQSW6zr mRzCiqj3StxtIUBBoFzbaDQiIsIb1IZbLHjh2SW4d8YMJCalYMkHH+Jf4WEYmtIN2VYLhjgl pDi8LkJxCZL37SC3qt4nvpWJTL14RVQUmA5RwPi+qQHvFB1HSaXu5lBBkBmAXsFRz8ya23At u0b5CGDC2+Kq9M5rJ0JkJf9hcjxB+JQtWBUTtLQVLqMJAUQgc0OzWTKb4XQ6kX/wIOY9/DBe XLFSaR86bDg2bd4Mk8mMh2fPxpNPP43P848oUVNMpwhlx7CnNRxpZiOSKWiMoa8RTuvBSiwQ pWKKD2lJe1DocWM/BXt7jlagrNqOxheFm8kvqZnrxTj1qmORT/+JeSkFuMb/ONhTS7czWDlM 4gB2F6eZ9vasLGZZwsPdVqtVjo6Ols/L7CfPuOceeduWb+TVL+fIUVFRimZWrVwp68mcWbNk rh5rXgH3QrTTDMpG7iOd6mMI9Lq4GuNa8V1mq8YJX56p02e+qs8JntxgpAevet9Yf64ji02x r9+bqnNjue2SFu41n4nqq+HP5HFD/PSPZYs3Tyctrg+4F7Ds+ed39h84YKfZZB4cabMhPSMD 4RHeDGnIsAtRXV2F+2fNwrS77kJMbCwmTp7c5ALCAmRnZyMnJwclx0oR2SkSyUlJGDRoIOrs DuTm5mLAgAHontoDX36xATZbJBK6xmPxkiXBTHp+kD66NSKM1WO84uPYnN4WxDhf7j5KlR3c zhG9Wh5qObtqtfTiVX/Iz/kEtmLa2MPN7f5dg9h0ITwgB5BtW7bIr69ZIxcfPSq3h9w3fXqw vyB6opUTFYwFAPtS9X1yuZzan+sHw7lusKJpqVwp3KjHOTjFFGZ5MmcG2u/w73awAIt5nL80 bzmfn6tpv4Pb+7ZEgHhCkdxOcqiwUP7808+U4x/37ZP3/bC3yfmLR44MRvllHKWL6tkfdIKw X0KAJK7eae/ZwOPUbddpxr7ZwnOXsqXwfX63HQiQzeNe0fQTcyJ+v3GM3dMzmvNDedx8Tbuw CpMIV/lMlbjAc+1lr15esQLjrrwCg7MGYfI1k/Hdzp2NERgFlpWVQaX1/+TNjgmEiVxrDyao DSbSPsqxxWto+mvlMB2iaf2nMPur/VxXkPYW3is4Vd9qYxagruB9xSXuKVzizuES8xG2Spdz yqt9oddX4l7E+wHvsrUQtYPxhCsl1b67qHP/VyfabbWcrKjA3r17sHz5cmSkZ2DhosafGZAr wc1TvAU1CjwxsH9/9OndW4kbjCYjTp6swv4f9x8sKCwclncgv4yebxwXYz5Ayz8tH8JFHRf7 v3Vo+Z1CYSUuYzMZzRaghPcetnKlTy+/HsFmP4nP72BzX8yB4EhefcJvf8hjknkT6h0mIQIE kkIPazQ1gzFMgniOCTYwiat4oUB1L7Ve72brY+B9jWXstlw+F+DDSIJDPk0iYojMfv1OZQMi FtCTn4uKJr69bh2yBg5ESE6zaAggcN/pIsCE8eMVxQ8dMlh+ZvFif0HlAt+zXDtpUkhBHUAA gafaW/kvLV+mKH/ihAmyy+Xy1+1F9XOECNBxBBB4sr2Uv23rVjmpWzf5srFj5Mrycn/dlmuf IUSAjiWAwIz2iAm+ys2V31671t/KdxPm690/RICOJ4DAcMKu0xQW5BEu9XfvEAFOvwRTstzC lbFZnB61h4jUbAGnbRtCaji7CQDORUXx/jx4//+AbWj93rPIifdwuVKUNBdy/hqSDpTW7h+X cxFBvErd0v8TWMdl0YMI/T+BZ638X4ABALiJt5GyzHDtAAAAAElFTkSuQmCC --------------070206040803090007060302-- --------------020707080904020408090704--

2 2

Re: [Engine-devel] [Engine-patches] Change in ovirt-host-deploy[master]: packaging: Fixed building RPMs on non-x86_64 architectures
by Leonardo Bianconi 31 Jul '13

31 Jul '13

Ok, no problem. Thanks >-----Original Message----- >From: Itamar Heim [mailto:iheim@redhat.com] >Sent: terça-feira, 30 de julho de 2013 16:30 >To: Leonardo Bianconi >Cc: Vitor de Lima >Subject: Re: [Engine-patches] Change in ovirt-host-deploy[master]: packaging: Fixed building RPMs on non-x86_64 architectures > >On 07/30/2013 10:26 PM, Leonardo Bianconi wrote: >> Hi Itamar! >> >> I'm working on the API change: >> >>>> I think setting it from cpu name automatically and having it read >>>> only makes sense API wise. >>>> GUI wise, i'm torn, but you could always make the API only accept >>>> the cpu, and let the user use the arch only to filter the cpu models, etc. >> >> I looked for how create a field read-only, but I didn't find anything in the wiki. So, I added the field 'Architecture' for cluster, getting it >from the CPU object. In the file rsdl_metadata.yaml I added the architecture field as optional for the cluster's requests (update and >add) and internally it is being defined by the CPU name, so when the architecture is sent in the xml, it is ignored. I tested it and it`s >working fine. >> >> Is this the read only behavior you expect for the API? > >can you please re-send with engine-devel in cc so i can cc the rest api maintainer easily? > >thanks > >> >> Regards. >> Leonardo Bianconi >> >>> -----Original Message----- >>> From: Vitor de Lima >>> Sent: terça-feira, 30 de julho de 2013 11:11 >>> To: Leonardo Bianconi >>> Subject: FW: [Engine-patches] Change in ovirt-host-deploy[master]: >>> packaging: Fixed building RPMs on non-x86_64 architectures >>> >>> >>> >>>> -----Original Message----- >>>> From: Itamar Heim [mailto:iheim@redhat.com] >>>> Sent: segunda-feira, 29 de julho de 2013 09:59 >>>> To: Vitor de Lima >>>> Subject: Re: [Engine-patches] Change in ovirt-host-deploy[master]: packaging: >>>> Fixed building RPMs on non-x86_64 architectures >>>> >>>> On 07/29/2013 03:38 PM, Vitor de Lima wrote: >>>>> Thanks, the problem is I had issues testing it on a x86_64 machine. >>>> Everything is OK right now and unfortunately I rebased the patches, >>>> so the code review must be done again. >>>>> >>>>> I have a question, the engine patch is in review process, after >>>>> adding the >>>> architecture field I thought a little bit about how the REST API >>>> would be changed, so far I have two options on how to integrate this >>>> new field. I could export the architecture field to the user of the >>>> API, so the resources would have the architecture field accessible >>>> to the user of the API. This can cause problems related to bad user >>>> input (like a cluster with a POWER cpu name and an architecture field defined to 'x86_64'). >>>>> >>>>> On other hand, I could hide this field and set its content >>>>> automatically >>>> (derived from the cpu name in clusters and from the selected cluster >>>> on VMs, Templates and Pools). Which approach would be the most appropriate? >>>> >>>> I think setting it from cpu name automatically and having it read >>>> only makes sense API wise. >>>> GUI wise, i'm torn, but you could always make the API only accept >>>> the cpu, and let the user use the arch only to filter the cpu models, etc. >>>> >>>>> >>>>>> -----Original Message----- >>>>>> From: Itamar Heim [mailto:iheim@redhat.com] >>>>>> Sent: sexta-feira, 26 de julho de 2013 00:08 >>>>>> To: Vitor de Lima >>>>>> Subject: Re: [Engine-patches] Change in ovirt-host-deploy[master]: >>>> packaging: >>>>>> Fixed building RPMs on non-x86_64 architectures >>>>>> >>>>>> On 07/24/2013 03:13 PM, vitor.lima(a)eldorado.org.br wrote: >>>>>>> Vitor de Lima has uploaded a new change for review. >>>>>>> >>>>>>> Change subject: packaging: Fixed building RPMs on non-x86_64 >>>>>>> architectures ...................................................................... >>>>>>> >>>>>>> packaging: Fixed building RPMs on non-x86_64 architectures >>>>>>> >>>>>>> The DMI decode is available only on the x86_64 architecture, the >>>>>>> spec file was changed to reflect this. >>>>>>> >>>>>>> Change-Id: I691544be6630ed2e88acbf8f1828b7995f582ffa >>>>>>> Signed-off-by: Vitor de Lima <vitor.lima(a)eldorado.org.br> >>>>>>> --- >>>>>>> M ovirt-host-deploy.spec.in >>>>>>> 1 file changed, 2 insertions(+), 0 deletions(-) >>>>>> >>>>>> >>>>>> hi vitor, >>>>>> >>>>>> just to make sure the status is clear - alon mentioned on both >>>>>> these >>>> patches >>>>>> to "please verify". this means he expects you to tick the 'verified' >>>>>> checkbox >>>> on >>>>>> the gerrit patch and commenting that you tested this works for >>>>>> you, >>>> doesn't >>>>>> break things, etc. >>>>>> once you do that, he can merge the patches (he already approved >>>>>> them) >>>>>> >>>>>> Thanks, >>>>>> Itamar >>

1 0

[Engine-devel] [ATN] oVirt 3.3 release, moving to RC [3.3 branching, blockers review]
by Moran Goldboim 30 Jul '13

30 Jul '13

This is a multi-part message in MIME format. --------------080603010209010007090703 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit We would like to go a head on oVirt 3.3 release process and issue an RC for tomorrow meeting: Maintainers/ Package owners ================== -branch your git repo (master) with 3.3 branch (making master ready for 3.4) -for tomorrow meeting, overview [1], see if you have any changes to it -if you don't have any blockers under your component, please branch 3.3 with RC1 branch | -master | -engine_3.3 | -RC1 | -engine_3.2 ... Users ==== with your experience from test day and with nightlies, if you feel there are additional candidates to block this version for please add it to the tracker bug [1]. Suggested Schedule ============ Wed Jul 31st - review of blockers for the version and component readiness Mon Aug 5th - RC1 release Wed Aug 7th - Release readiness review (in case of blockers an RC2 will be issued) Thanks. [1]*Bug 918494* <https://bugzilla.redhat.com/show_bug.cgi?id=918494> -Tracker: oVirt 3.3 release --------------080603010209010007090703 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 would like to go a head on oVirt 3.3 release process and issue an RC <br> <br> for tomorrow meeting:<br> <br> Maintainers/ Package owners <br> ==================<br> -branch your git repo (master) with 3.3 branch (making master ready for 3.4)<br> -for tomorrow meeting, overview [1]<span id="summary_alias_container"><span id="short_desc_nonedit_display">, see if you have any changes to it<br> -if you don't have any blockers under your component, please branch 3.3 with RC1 branch<br> <br>     |    <br>     -master<br>     |    <br>     -engine_3.3<br>         |<br>         -RC1<br>     |<br>     -engine_3.2<br>     ...<br>    <br> Users<br> ====<br> with your experience from test day and with nightlies, if you feel there are additional candidates to block this version for please add it to the tracker bug [1].<br> <br> Suggested Schedule<br> ============<br> Wed Jul 31st - review of blockers for the version and component readiness<br> Mon Aug 5th - RC1 release<br> Wed Aug 7th - Release readiness review (in case of blockers an RC2 will be issued)<br> </span></span><span id="summary_alias_container"><span id="short_desc_nonedit_display"><span id="summary_alias_container"><span id="short_desc_nonedit_display"><br> Thanks.</span></span> <br> <br> [1]</span></span><a href="https://bugzilla.redhat.com/show_bug.cgi?id=918494"><b>Bug 918494</b></a> -<span id="summary_alias_container"> <span id="short_desc_nonedit_display">Tracker: oVirt 3.3 release<br> <br> <br> </span></span> </body> </html> --------------080603010209010007090703--

4 5

[Engine-devel] Question about the attribute lunType (LUNs)
by Gustavo Frederico Temple Pedrosa 30 Jul '13

30 Jul '13

--_000_EF26FC1776F7FF46BFC072393EFD13A29A07E9SERV070corpeldora_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello everyone, The QEMU/KVM on IBM POWER does not support iSCSI yet. This requires the imp= lementation of methods that evaluate if a Disk is a iSCSI LUN or not, in or= der to avoid its use in this specific architecture. Looks like this can be determined by the attribute lunType (which is of the= type StorageType, an Enum) of the class LUNs. But when I retrieve the obje= ct, the attribute lunType has the value "UNKNOWN", even if I've setted it w= ith another value. In the class LunDAODbFacadeImpl there is not a call to t= he "entity.setLunType" method. Does anyone know how to retrieve the attribute lunType? Is the "UNKNOW" val= ue a bug? Thanks, Leonardo Bianconi/Vitor de Lima/Gustavo Pedrosa --_000_EF26FC1776F7FF46BFC072393EFD13A29A07E9SERV070corpeldora_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)"> <style></style> </head> <body lang=3D"PT-BR" link=3D"blue" vlink=3D"purple"> <div class=3D"WordSection1"> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black;mso-fareas= t-language:ZH-CN">Hello everyone,<br> <br> The QEMU/KVM on IBM POWER does not support iSCSI yet. This requires the imp= lementation of methods that evaluate if a Disk is a iSCSI LUN or not, in or= der to avoid its use in this specific architecture.<br> Looks like this can be determined by the attribute lunType (which is of the= type StorageType, an Enum) of the class LUNs. But when I retrieve the obje= ct, the attribute lunType has the value "UNKNOWN", even if I've s= etted it with another value. In the class LunDAODbFacadeImpl there is not a call to the "entity.setLunType&quot= ; method.<br> <br> Does anyone know how to retrieve the attribute lunType? Is the "UNKNOW= " value a bug?<br> <br> </span><span style=3D"color:black;mso-fareast-language:ZH-CN">Thanks,</span= ><span style=3D"mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p class=3D"MsoNormal">Leonardo Bianconi/Vitor de Lima/Gustavo Pedrosa<o:p>= </o:p></p> </div> </body> </html> --_000_EF26FC1776F7FF46BFC072393EFD13A29A07E9SERV070corpeldora_--

3 5

[Engine-devel] VNIC profiles & Device Custom Properties
by Amihay Winter 29 Jul '13

29 Jul '13

------=_Part_11407198_1454246753.1374581565910 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hi all, I'm building a TCMS plan for the Device Custom Properties feature and I came across some questions. I'm sorry that I'm a little late with my thoughts but I hope you'll still hear them out. Also, I know It's a little long but please bear with me :) I want to talk about two things: 1. Sending an updateDevice verb whenever clicking on "Edit" and than "OK". 2. Setting Port Mirroring at the configuring of a nic and not at the profile. 1.According to the Vnic_Profiles's wiki (in the Editing a profile section) it says: "The changes will seep down to all VNICs using the profile. In case VNIC using the edited profile are connected to running VMs, the change will apply only on the VM next run." I'll describe a Scenario: Creating profile A with property speed = 500 Setting vnic2 on vm to have profile A (using Hotplugnic) Changing (in the profile) speed = 700 According to the Vnic_Profiles's wiki, only when I restart my vm I'll get my setting right. In my opinion, If we could enable the update of those setting LIVE we will give the clients a better solution in the Vnic Profiles. I will be able to update all of my 1000 vms in a few minutes with a single script instead of restarting them all and maybe stopping others' work. I think that restarting 1000 vms because I want to set a property is not something that an admin would want to do. One way to implement it is to send a verb "updateDevice" each time we open the the "Edit" window and clicking "OK" I guess that when the design of update device was made, we tried to send minimal verbs, but in this case, I think that if a user clicked on "Edit" & "OK" then he wanted to send the verb, otherwise, he would have pressed on "Edit" & "Cancel". Sending this verb will allow us to keep the vms update with, in my opinion, minimum cost and with great profit - Giving the client a "more correct environment" LIVE. 2. I'll start with saying that in my opinion, the Vnic Profile feature was created to give the client a *more dynamic network environment* and I support. But, I think that the statical variables like MAC, Un/Pluged and Port Mirroring which always exist should be at the nic and not in the profile. In my opinion, Profile's properties may have: max_mtu, min_mtu, mtu, speed, id, vlan... Identifiers for the network. Maybe I'm missing something but it seems natural to me that the port mirroring will be at nic and not at the profile. I'll really appreciate comments. Thank you for your time. Amihay Winter ----- Original Message ----- > ----- Forwarded Message ----- > From: "Livnat Peer" <lpeer(a)redhat.com> > To: "Moti Asayag" <masayag(a)redhat.com> > Cc: "engine-devel" <engine-devel(a)ovirt.org>, "Ofri Masad" > <omasad(a)redhat.com>, "Mike Kolesnik" <mkolesni(a)redhat.com>, "Oved Ourfalli" > <oourfali(a)redhat.com> > Sent: Monday, July 8, 2013 10:11:15 AM > Subject: Re: VNIC profiles > On 07/08/2013 12:36 AM, Moti Asayag wrote: > > I've updated the wiki accordingly and added few comments inline. > > > > ----- Original Message ----- > >> From: "Livnat Peer" <lpeer(a)redhat.com> > >> To: "Moti Asayag" <masayag(a)redhat.com> > >> Cc: "engine-devel" <engine-devel(a)ovirt.org>, "Ofri Masad" > >> <omasad(a)redhat.com>, "Mike Kolesnik" <mkolesni(a)redhat.com>, > >> "Oved Ourfalli" <oourfali(a)redhat.com> > >> Sent: Sunday, July 7, 2013 2:59:34 PM > >> Subject: Re: VNIC profiles > >> > >> On 07/07/2013 01:59 PM, Moti Asayag wrote: > >>> Hi, > >>> > >>> I've updated the wiki with the feedbacks from this thread, added a > >>> backend > >>> section naming the affected commands and also add added few questions of > >>> my own embedded in the pastedtext below. > >>> > >> > >> Hi Moti, > >> A good and comprehensive description of the feature behavior. > >> See my comments bellow - > >> > >>> In addition, another question here: > >>> > >>> The units within the UI mockups are Mb and Mbps. The libvirt APIs expects > >>> the units to be in kb and kbps. Which component is responsible to convert > >>> them to the expect units ? engine or VDSM ? > >> > >> Giuseppe mentioned that in a previous thread on this subject. > >> Ofri and Giuseppe agreed that the translation would be done on the > >> engine level. > >> > >> > >>> > >>> Copied text from the wiki: > >>> > >>> Adding a Profile > >>> > >>> The network administrator could create several VNIC Profiles for each > >>> network. He could then grant a users with the permission to use (consume) > >>> each profile. The user will only be able to use profiles which he was > >>> granted access to. > >>> > >>> For example: the network admin will create two VNIC profiles for > >>> network "blue": > >>> > >>> Profile "Gold" - with better QoS and with port mirroring > >>> Profile "Silver" with lower QoS and without port mirroring. > >>> > >> > >> I would use other names for the profiles to avoid confusion. > >> Gold and Silver are likely to be QoS object names, a more typical name > >> for a network profile is - teachers-blue and students-blue > >> > >> The different profiles can have different QoS (teachers-blue would get > >> Gold QoS while Students-blue will have Silver). > >> > >> > >>> He will then define the user-group "students" as user of profile > >>> "Silver" and user-group "teachers" as user of profile "Gold". In this > >>> case the teachers will enjoy better quality of service then the > >>> students. When a teacher will add/edit a virtual NIC he could select > >>> profile "Gold" for that NIC - the VNIC will be connected to network > >>> "blue" with high QoS and with port mirroring. > >>> > >>> Question: In the same matter we allowed via the UI to grant 'NetworkUser' > >>> to 'everyone' user, wouldn't it ease the use of Profiles if we support it > >>> in this context as well? > >> > >> The ease of use could be that when creating a network we'll display in > >> the UI all VNIC-QoS-objects and the users could tick next to the QoS > >> they are interested in, for each QoS that was chosen a profile would be > >> created. > >> > >> I would enhance that with youe suggestion above and display next to the > >> QoS that was checked the option to mark 'Allow All users' like we have > >> today for making a network public, this option would give permission to > >> everyone on that profile. > >> > >> > >>> > >>> Editing a Profile > >>> > >>> A user should be able to edit the profile properties (including profile > >>> name) while VMs are attached and are using this Profile (reference > >>> should be done by id). > >>> Changing the network of a vNic profile will be allowed only if no VMs > >>> are using the profile. > >> > >> It would be better if we can limit this to no running VM is using the > >> profile (or more simple to implement if all VMs that are using this > >> profile are in status down). > > > > Allowing to delete a vnic profile when used by vms is asymmetric to the > > network removal > > when it is used by vms or templates. Today the update network operation is > > blocked for that. > > In addition, with the suggest simplification to remove a profile when no > > running vms, the user > > will have to find for himself if the profile is being used prior to its > > removal since the > > operation will not be blocked. > > > > If we allow to delete a vnic profile, when a vm is using it (regardless the > > VM status) > > we'll have to update the VM entity as well in that operation: since we do > > not support a > > network with 'none' profile, we'll have to delete the network as well. > > > > If we'll remove a vnic profile in 3.1 cluster, used by vms in status down, > > we'd find a case > > in which a VM is attached to a 'none' network. This is unsupported in 3.1 > > cluster. We can block > > such operation, but this is another motivation why we'd better not to allow > > removing a used profile. > > > The context above is about editing not deleting :) > I agree with what you wrote if the context was remove. > >> > >>> Since we have no way to distinguish between running and current > >>> configurations, the expected behavior of such a change is > >>> unpredictable and less intuitive to the user (especially since > >>> dynamic wiring is supported). > >>> The changes will seep down to all VNICs using the profile. > >>> In case VNIC using the edited profile are connected to running VMs, > >>> the change will apply only on the VM next run. > >>> > >>> Question: What about Hibernate/Suspend VM ? will the resume VM action > >>> uses > >>> the original configuration for the vnics when the VM was started ? > >> > >> Currently profile includes: network, port-mirroring, custom property, QoS > >> > >> Changing any of the above (except for network) requires a VM reboot, so > >> I think that we can start with the following statement - the profile > >> change would only apply after next VM reboot. > >> > >> There are 2 problems with the above: > >> - Today we support network wiring, with VNIC profiles we are asking the > >> users to create a new profile and attach the VMs to the new profile, I > >> can see the RFE coming - we can report that ourselves ;) > >> > >> - We don't reflect with which configuration the VM is running, e.g we > >> edited the profile QoS but I'm not sure with which QoS the VM is > >> currently running. (The RFE for differentiating between current > >> configuration and running configuration was already asked for by > >> numerous users) > >> > >> The above is a general issue that we need to solve and I would not limit > >> editing VNIC profiles because of it. > >> We can mitigate this specifically for QoS like described bellow. > >> > >> > >> > >>> Deleting a Profile > >>> > >>> VNIC Profiles could not be deleted from the engine as long as one or more > >>> VM/Templates are using those profiles. > >> > >>> Reporting vNic actual configuration > >>> > >>> The engine will retrieve the actual configuration of the profile > >>> properties on the VNIC from VDSM (using the network statistics > >>> mechanism) and the networked administrator will be presented with the > >>> state of each VNIC (synched/unsynched). > >>> > >> > >> Will the admin be able to see the actual values? I think the synced > >> property is not enough (I'm not sure how interesting this property is to > >> start with). > > > > We can extend the VmGuestAgentInterface to contain the actual value, so > > they > > will be presented for each vnic in the 'guest data' sub-tab. > > > AFAIU this info does not come from the guest it is info we retrieve from > libvirt. > The VmGuestAgentInterface should be used only for information reported > by the guest, information whose credibility can be questioned. > >> > >>> Editing a VNIC / Changing a VNIC profile > >>> > >>> Changing the profile a VM is using while the VM is running should > >>> behave like dynamic wiring (changing the VM network while it is > >>> running). > >>> Hot-plug of a vnic will will use will use the updated profile connected > >>> to the VNIC. > >>> > >> > >> Not sure I fully understand the sentence above. > >> Hot plug will be fully supported, you can choose any profile (you have > >> permissions on) while plugging a new device. > >> > > > > That was the intention. seems like an edgy hand syndrome :) > > Changed to: > > * Hot plug will be fully supported: the user can choose any permitted > > profile while plugging a new device or when activating an existing one. > > > >>> Adding a Network > >>> > >>> When adding a network, a user can provide an option to create a vNic > >>> Profile for it. > >>> > >>> Question: Is it s default profile ? what are its properties ? > >>> Question: What about 'Public Use' option ? Are they still relevant in the > >>> context of adding new networks or we should eliminate them and move it > >>> only to 'Add vNic Profile' dialog? > >>> > >> > >> see previous comments > >> In addition when creating a profile we should have 'Allow all' for > >> implicitly creating permissions, like we have today for network. > >> > >>> Updating a Network > >>> > >>> When a network role is modified to be a 'non-VM network', all vNic > >>> profiles > >>> associated with it should be deleted. > >> > >> And permissions associated with these profiles > >> > >>> Removing a Network > >>> > >>> Should remove all profiles on that network > >>> > >> > >> And associated permissions > >> > >>> Adding an Empty Data-Center > >>> > >>> Currently, When creating a new Data-Center, the management network is > >>> automatically created. > >>> From 3.3, a default vNic profile will be created for the management > >>> network. > >>> > >>> VM snapshot/import/export > >>> > >>> We should handle VMs that are pointing to a network directly for > >>> backward compatibility. > >>> We need to select first profile that is on that network that the user > >>> has permissions on. > >>> > >>> Question: Do we wish to support it export from 3.3 and import to 3.2 or > >>> below? > >> > >> That means that when you write a VM in the OVF you need to write network > >> in addition to profile. > >> > > > > The network name is already there, so when importing a vnic from 3.3 to an > > earlier version > > the profile name will be ignored. > > > >> > >>> Question: A user can import/export a VM/Template even if he doesn't have > >>> permissions on the networks. Is the next flow valid ? > >>> > >>> The profile name should be saved in the OVF (in addition to the network > >>> name which is saved today). > >>> During import, if both (network name, profile name) exist on the target > >>> DC, the vnic will get the profile id. > >>> If the network exists in the Data-Center, but has no profile as > >>> specified in the OVF, the user will be notified (event log) and the > >>> VNIC will be connected to a default minimal profile defined in the > >>> system, regardless the permissions the user has on the network. > >>> > >> > >> What is a 'default minimal profile' ? I would rather have a VNIC with no > >> profile associated with it. > > > > The 'default minimal profile' refers to a vnic profile with the lower > > average bandwidth. > > > > With the approach you've suggested, any imported VM/Template from an > > earlier to 3.3 version > > will require a manual intervention in order to configure a network to the > > VM. > I should have elaborated some more - > If a VM has a profile then we should look up this specific profile, if > such a profile does not exists then import the VM with profile none like > we do today for VM's with reference to a network that does not exist on > the setup. > If a VM does not have a profile (3.2 and lower versions) we should look > into the network name, if this network exist and we have a profile with > permissions to the user then use this profile (if there is more than one > choose one randomly). > > And for 3.1 we'll have to drop such vnics since network 'none' isn't > > supported. > > > >> > >>> If failed to find any matching vNic profile, the vnic's profile will be > >>> set > >>> with 'none'. > >>> > >>> When a Template is created from a VM the VNIC Profile will be kept > >>> along with the VNIC. When a VM is created from template the VNIC > >>> Profiles will be taken from the template's VNICs. > >>> > >>> ----- Original Message ----- > >>>> From: "Livnat Peer" <lpeer(a)redhat.com> > >>>> To: "engine-devel" <engine-devel(a)ovirt.org>, "Ofri Masad" > >>>> <omasad(a)redhat.com> > >>>> Cc: "Mike Kolesnik" <mkolesni(a)redhat.com>, "Moti Asayag" > >>>> <masayag(a)redhat.com>, "Oved Ourfalli" <oourfali(a)redhat.com> > >>>> Sent: Sunday, June 30, 2013 3:59:37 PM > >>>> Subject: VNIC profiles > >>>> > >>>> Hi, > >>>> > >>>> We are working on adding VNIC profiles as part of the work to add VNIC > >>>> QoS. > >>>> > >>>> http://www.ovirt.org/Features/Network_QoS#VNIC_Profiles > >>>> > >>>> We need to define some of the system behavior followed by this change, > >>>> here is my take - > >>>> > >>>> Editing a profile - > >>>> -------------------- > >>>> A user should be able to edit the profile properties (including profile > >>>> name) while VMs are attached and are using this Profile (reference > >>>> should be done by id). > >>>> > >>>> Changing the network though is a bit more tricky as long as we don't > >>>> have a way to distinguish between running and current configurations I > >>>> think it could be very confusing to the user. Especially since we > >>>> support dynamic wiring so the behavior IMO is unpredictable. > >>>> I think it should be blocked at this point. > >>>> > >>>> > >>>> Edit a VNIC / change a VNIC profile - > >>>> ------------------------------------ > >>>> Changing the profile a VM is using while the VM is running should behave > >>>> like dynamic wiring (changing the VM network while it is running). > >>>> > >>>> > >>>> Remove a Profile - > >>>> ------------------- > >>>> Is only valid if all VMs that are using this profile are in status down. > >>>> It should update all VMs to point to no profile which should behave like > >>>> none network today. > >>>> > >>>> I see no reason to support a profile on a none network at this point. > >>>> > >>>> The above is also relevant for upgrade flow (upgrading none network to > >>>> point to no profile) > >>>> > >>>> > >>>> Removing a Network - > >>>> ---------------------- > >>>> should remove all profiles on that network > >>>> > >>>> > >>>> VM snapshot/import/export - > >>>> -------------------------- > >>>> We should handle VMs that are pointing to a network directly for b/w > >>>> compatibility. > >>>> we need to select first profile that is on that network that the user > >>>> has permissions on. > >>>> > >>>> > >>>> I assume there are more, comments are welcome > >>>> > >>>> Thanks, Livnat > >>>> > >>>> > >> > >> ------=_Part_11407198_1454246753.1374581565910 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html><body><div style=3D"font-family: times new roman, new york, times, se= rif; font-size: 12pt; color: #000000"><div><br></div><div>Hi all,<br></div>= <div><br></div><div>I'm building a TCMS plan for the <span dir=3D"auto">Dev= ice Custom Properties feature and I came across some questions.</span><br><= /div><div>I'm sorry that I'm a little late with my thoughts but I hope you'= ll still hear them out.<br></div><div>Also, I know It's a little long but p= lease bear with me :)<br></div><div><div><br></div><div>I want to talk abou= t two things:<br></div><div>1. Sending an updateDevice verb whenever clicki= ng on "Edit" and than "OK".<br></div><div>2. Setting Port Mirroring at the = configuring of a nic and not at the profile.<br></div><div><br></div><div>1= .According to the Vnic_Profiles's wiki (in the Editing a profile section) i= t says:</div><div>      "The changes will seep down to = all VNICs using the profile.</div><div>      &nbsp= ; In case VNIC using the edited profile are connected to running VMs, = the change will apply only on the VM next run."<br></div><div>  &= nbsp; I'll describe a Scenario:</div><div>     &nb= sp; Creating profile A with property speed =3D 500 <br></div><div> &nb= sp;     Setting vnic2 on vm to have profile A (using Ho= tplugnic)</div><div>       Changing (in the profil= e) speed =3D 700</div><div>    According to the Vnic_Profile= s's wiki, only when I restart my vm I'll get my setting right.</div><div>&n= bsp;   In my opinion, If we could enable the update of those sett= ing LIVE we will give the clients a better solution in the Vnic Profiles.<b= r></div><div>    I will be able to update all of my 1000 vms= in a few minutes with a single script instead of restarting them all and m= aybe stopping others' work.<br></div><div>    I think that r= estarting 1000 vms because I want to set a property is not something that a= n admin would want to do.<br></div><div>     &nbsp= ;  </div><div>    One way to implement it is to se= nd a verb "updateDevice" each time we open the the "Edit" window and clicki= ng "OK"</div><div>    I guess that when the design of update= device was made, we tried to send minimal verbs, but in this case, I think= that if a user clicked on "Edit" & "OK" then he wanted to send the ver= b, otherwise, he would have pressed on "Edit" & "Cancel".</div><div><br= ></div><div>    Sending this verb will allow us to keep the = vms update with, in my opinion, minimum cost and with great profit - Giving= the client a "more correct environment"  LIVE.</div><div><br></div><d= iv>2. I'll start with saying that in my opinion, the Vnic Profile feature w= as created to give the client a *more dynamic network environment* and I su= pport.</div><div>    But, I think that the statical var= iables like MAC, Un/Pluged and Port Mirroring which always exist should be = at the nic and not in the profile.</div><div>    In my opini= on, Profile's properties may have: max_mtu, min_mtu, mtu, speed, id, vlan..= . Identifiers for the network.</div><div>    Maybe I'm missi= ng something but it seems natural to me that the port mirroring will be at = nic and not at the profile.</div><div><br></div><div><br></div><div><span i= d=3D"result_box" class=3D"short_text" lang=3D"en"><span class=3D"hps alt-ed= ited">I'll really appreciate comments.</span></span></div><div><span id=3D"= result_box" class=3D"short_text" lang=3D"en"><span class=3D"hps alt-edited"= >Thank you for your time.</span></span></div><div>Amihay Winter<br> &n= bsp;           &nbsp= ; </div><br></div><hr id=3D"zwchr"><blockquote style=3D"border-left:2p= x solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:nor= mal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans= -serif;font-size:12pt;">----- Forwarded Message -----<br>From: "Livnat Peer= " <lpeer(a)redhat.com><br>To: "Moti Asayag" <masayag(a)redhat.com><= br>Cc: "engine-devel" <engine-devel(a)ovirt.org>, "Ofri Masad" <omas= ad(a)redhat.com>, "Mike Kolesnik" <mkolesni(a)redhat.com>, "Oved Ourfa= lli" <oourfali(a)redhat.com><br>Sent: Monday, July 8, 2013 10:11:15 AM<= br>Subject: Re: VNIC profiles<br><div><br></div>On 07/08/2013 12:36 AM, Mot= i Asayag wrote:<br>> I've updated the wiki accordingly and added few com= ments inline.<br>> <br>> ----- Original Message -----<br>>> Fro= m: "Livnat Peer" <lpeer(a)redhat.com><br>>> To: "Moti Asayag" &lt= ;masayag(a)redhat.com><br>>> Cc: "engine-devel" <engine-devel@ovi= rt.org>, "Ofri Masad" <omasad(a)redhat.com>, "Mike Kolesnik" <mko= lesni(a)redhat.com>,<br>>> "Oved Ourfalli" <oourfali(a)redhat.com&g= t;<br>>> Sent: Sunday, July 7, 2013 2:59:34 PM<br>>> Subject: R= e: VNIC profiles<br>>><br>>> On 07/07/2013 01:59 PM, Moti Asaya= g wrote:<br>>>> Hi,<br>>>><br>>>> I've updated t= he wiki with the feedbacks from this thread, added a backend<br>>>&gt= ; section naming the affected commands and also add added few questions of<= br>>>> my own embedded in the pastedtext below.<br>>>><br= >>><br>>> Hi Moti,<br>>> A good and comprehensive descrip= tion of the feature behavior.<br>>> See my comments bellow -<br>>&= gt;<br>>>> In addition, another question here:<br>>>><br>= >>> The units within the UI mockups are Mb and Mbps. The libvirt A= PIs expects<br>>>> the units to be in kb and kbps. Which component= is responsible to convert<br>>>> them to the expect units ? engin= e or VDSM ?<br>>><br>>> Giuseppe mentioned that in a previous t= hread on this subject.<br>>> Ofri and Giuseppe agreed that the transl= ation would be done on the<br>>> engine level.<br>>><br>>&gt= ;<br>>>><br>>>> Copied text from the wiki:<br>>>&gt= ;<br>>>> Adding a Profile<br>>>><br>>>> The netw= ork administrator could create several VNIC Profiles for each<br>>>&g= t; network. He could then grant a users with the permission to use (consume= )<br>>>> each profile. The user will only be able to use profiles = which he was<br>>>> granted access to.<br>>>><br>>>= >     For example: the network admin will create two VNIC prof= iles for<br>>>>     network "blue":<br>>>><br>&= gt;>>         Profile "Gold" - with better QoS an= d with port mirroring<br>>>>         Profile "= Silver" with lower QoS and without port mirroring.<br>>>><br>>&= gt;<br>>> I would use other names for the profiles to avoid confusion= .<br>>> Gold and Silver are likely to be QoS object names,  a mo= re typical name<br>>> for a network profile is - teachers-blue and st= udents-blue<br>>><br>>> The different profiles can have differe= nt QoS (teachers-blue would get<br>>> Gold QoS while Students-blue wi= ll have Silver).<br>>><br>>><br>>>>     He w= ill then define the user-group "students" as user of profile<br>>>&gt= ;     "Silver" and user-group "teachers" as user of profile "Gold= ". In this<br>>>>     case the teachers will enjoy bette= r quality of service then the<br>>>>     students. When = a teacher will add/edit a virtual NIC he could select<br>>>> &nbsp= ;   profile "Gold" for that NIC - the VNIC will be connected to networ= k<br>>>>     "blue" with high QoS and with port mirrorin= g.<br>>>><br>>>> Question: In the same matter we allowed = via the UI to grant 'NetworkUser'<br>>>> to 'everyone' user, would= n't it ease the use of Profiles if we support it<br>>>> in this co= ntext as well?<br>>><br>>> The ease of use could be that when c= reating a network we'll display in<br>>> the UI all VNIC-QoS-objects = and the users could tick next to the QoS<br>>> they are interested in= , for each QoS that was chosen a profile would be<br>>> created.<br>&= gt;><br>>> I would enhance that with youe suggestion above and dis= play next to the<br>>> QoS that was checked the option to mark 'Allow= All users' like we have<br>>> today for making a network public, thi= s option would give permission to<br>>> everyone on that profile.<br>= >><br>>><br>>>><br>>>> Editing a Profile<br>&= gt;>><br>>>>     A user should be able to edit the= profile properties (including profile<br>>>>     name) = while VMs are attached and are using this Profile (reference<br>>>&gt= ;     should be done by id).<br>>>>     Changi= ng the network of a vNic profile will be allowed only if no VMs<br>>>= >     are using the profile.<br>>><br>>> It would = be better if we can limit this to no running VM is using the<br>>> pr= ofile (or more simple to implement if all VMs that are using this<br>>&g= t; profile are in status down).<br>> <br>> Allowing to delete a vnic = profile when used by vms is asymmetric to the network removal<br>> when = it is used by vms or templates. Today the update network operation is block= ed for that.<br>> In addition, with the suggest simplification to remove= a profile when no running vms, the user<br>> will have to find for hims= elf if the profile is being used prior to its removal since the <br>> op= eration will not be blocked.<br>> <br>> If we allow to delete a vnic = profile, when a vm is using it (regardless the VM status) <br>> we'll ha= ve to update the VM entity as well in that operation: since we do not suppo= rt a<br>> network with 'none' profile, we'll have to delete the network = as well.<br>> <br>> If we'll remove a vnic profile in 3.1 cluster, us= ed by vms in status down, we'd find a case <br>> in which a VM is attach= ed to a 'none' network. This is unsupported in 3.1 cluster. We can block<br= >> such operation, but this is another motivation why we'd better not to= allow removing a used profile.<br>> <br><div><br></div>The context abov= e is about editing not deleting :)<br>I agree with what you wrote if the co= ntext was remove.<br><div><br></div>>><br>>>>     =     Since we have no way to distinguish between running and curre= nt<br>>>>         configurations, the expected= behavior of such a change is<br>>>>         u= npredictable and less intuitive to the user (especially since<br>>>&g= t;         dynamic wiring is supported).<br>>>&gt= ;     The changes will seep down to all VNICs using the profile.<= br>>>>         In case VNIC using the edited p= rofile are connected to running VMs,<br>>>>       &= nbsp; the change will apply only on the VM next run.<br>>>><br>&gt= ;>> Question: What about Hibernate/Suspend VM ? will the resume VM ac= tion uses<br>>>> the original configuration for the vnics when the= VM was started ?<br>>><br>>> Currently profile includes: netwo= rk, port-mirroring, custom property, QoS<br>>><br>>> Changing a= ny of the above (except for network) requires a VM reboot, so<br>>> I= think that we can start with the following statement - the profile<br>>= > change would only apply after next VM reboot.<br>>><br>>> = There are 2 problems with the above:<br>>> - Today we support network= wiring, with VNIC profiles we are asking the<br>>> users to create a= new profile and attach the VMs to the new profile, I<br>>> can see t= he RFE coming - we can report that ourselves ;)<br>>><br>>> - W= e don't reflect with which configuration the VM is running, e.g we<br>>&= gt; edited the profile QoS but I'm not sure with which QoS the VM is<br>&gt= ;> currently running. (The RFE for differentiating between current<br>&g= t;> configuration and running configuration was already asked for by<br>= >> numerous users)<br>>><br>>> The above is a general iss= ue that we need to solve and I would not limit<br>>> editing VNIC pro= files because of it.<br>>> We can mitigate this specifically for QoS = like described bellow.<br>>><br>>><br>>><br>>>> = Deleting a Profile<br>>>><br>>>> VNIC Profiles could not = be deleted from the engine as long as one or more<br>>>> VM/Templa= tes are using those profiles.<br>>><br>>>> Reporting vNic ac= tual configuration<br>>>><br>>>>     The engine= will retrieve the actual configuration of the profile<br>>>> &nbs= p;   properties on the VNIC from VDSM (using the network statistics<br= >>>>     mechanism) and the networked administrator will= be presented with the<br>>>>     state of each VNIC (sy= nched/unsynched).<br>>>><br>>><br>>> Will the admin be= able to see the actual values? I think the synced<br>>> property is = not enough (I'm not sure how interesting this property is to<br>>> st= art with).<br>> <br>> We can extend the VmGuestAgentInterface to cont= ain the actual value, so they<br>> will be presented for each vnic in th= e 'guest data' sub-tab.<br>> <br><div><br></div>AFAIU this info does not= come from the guest it is info we retrieve from<br>libvirt.<br>The VmGuest= AgentInterface should be used only for information reported<br>by the guest= , information whose credibility can be questioned.<br><div><br></div><br>&g= t;><br>>>> Editing a VNIC / Changing a VNIC profile<br>>>= ><br>>>>     Changing the profile a VM is using while= the VM is running should<br>>>>     behave like dynamic= wiring (changing the VM network while it is<br>>>>     = running).<br>>>>     Hot-plug of a vnic will will use wi= ll use the updated profile connected<br>>>>     to the V= NIC.<br>>>><br>>><br>>> Not sure I fully understand th= e sentence above.<br>>> Hot plug will be fully supported, you can cho= ose any profile (you have<br>>> permissions on) while plugging a new = device.<br>>><br>> <br>> That was the intention. seems like an = edgy hand syndrome :)<br>> Changed to:<br>>  * Hot plug will be = fully supported: the user can choose any permitted profile while plugging a= new device or when activating an existing one.<br>> <br>>>> Ad= ding a Network<br>>>><br>>>>     When adding a = network, a user can provide an option to create a vNic<br>>>> &nbs= p;   Profile for it.<br>>>><br>>>> Question: Is it s= default profile ? what are its properties ?<br>>>> Question: What= about 'Public Use' option ? Are they still relevant in the<br>>>>= context of adding new networks or we should eliminate them and move it<br>= >>> only to 'Add vNic Profile' dialog?<br>>>><br>>>= <br>>> see previous comments<br>>> In addition when creating a = profile we should have 'Allow all' for<br>>> implicitly creating perm= issions, like we have today for network.<br>>><br>>>> Updati= ng a Network<br>>>><br>>>> When a network role is modifie= d to be a 'non-VM network', all vNic profiles<br>>>> associated wi= th it should be deleted.<br>>><br>>> And permissions associated= with these profiles<br>>><br>>>> Removing a Network<br>>= >><br>>>>     Should remove all profiles on that n= etwork<br>>>><br>>><br>>> And associated permissions<b= r>>><br>>>> Adding an Empty Data-Center<br>>>><br>&= gt;>>     Currently, When creating a new Data-Center, the m= anagement network is<br>>>>     automatically created.<b= r>>>>     From 3.3, a default vNic profile will be creat= ed for the management<br>>>>     network.<br>>>&gt= ;<br>>>> VM snapshot/import/export<br>>>><br>>>>=     We should handle VMs that are pointing to a network directly= for<br>>>>     backward compatibility.<br>>>> =     We need to select first profile that is on that network that = the user<br>>>>     has permissions on.<br>>>><= br>>>> Question: Do we wish to support it export from 3.3 and impo= rt to 3.2 or<br>>>> below?<br>>><br>>> That means that= when you write a VM in the OVF you need to write network<br>>> in ad= dition to profile.<br>>><br>> <br>> The network name is already= there, so when importing a vnic from 3.3 to an earlier version<br>> the= profile name will be ignored.<br>> <br>>><br>>>> Questio= n: A user can import/export a VM/Template even if he doesn't have<br>>&g= t;> permissions on the networks. Is the next flow valid ?<br>>>&gt= ;<br>>>>     The profile name should be saved in the OVF= (in addition to the network<br>>>>     name which is sa= ved today).<br>>>>     During import, if both (network n= ame, profile name) exist on the target<br>>>>     DC, th= e vnic will get the profile id.<br>>>>     If the networ= k exists in the Data-Center, but has no profile as<br>>>>   &= nbsp; specified in the OVF, the user will be notified (event log) and the<b= r>>>>     VNIC will be connected to a default minimal pr= ofile defined in the<br>>>>     system, regardless the p= ermissions the user has on the network.<br>>>><br>>><br>>= > What is a 'default minimal profile' ? I would rather have a VNIC with = no<br>>> profile associated with it.<br>> <br>> The 'default mi= nimal profile' refers to a vnic profile with the lower average bandwidth.<b= r>> <br>> With the approach you've suggested, any imported VM/Templat= e from an earlier to 3.3 version <br>> will require a manual interventio= n in order to configure a network to the VM.<br><div><br></div>I should hav= e elaborated some more -<br><div><br></div>If a VM has a profile then we sh= ould look up this specific profile, if<br>such a profile does not exists th= en import the VM with profile none like<br>we do today for VM's with refere= nce to a network that does not exist on<br>the setup.<br><div><br></div>If = a VM does not have a profile (3.2 and lower versions) we should look<br>int= o the network name, if this network exist and we have a profile with<br>per= missions to the user then use this profile (if there is more than one<br>ch= oose one randomly).<br><div><br></div><br>> And for 3.1 we'll have to dr= op such vnics since network 'none' isn't supported.<br>> <br>>><br= >>>> If failed to find any matching vNic profile, the vnic's profi= le will be set<br>>>> with 'none'.<br>>>><br>>>>=     When a Template is created from a VM the VNIC Profile will b= e kept<br>>>>     along with the VNIC. When a VM is crea= ted from template the VNIC<br>>>>     Profiles will be t= aken from the template's VNICs.<br>>>><br>>>> ----- Origi= nal Message -----<br>>>>> From: "Livnat Peer" <lpeer(a)redhat.= com><br>>>>> To: "engine-devel" <engine-devel(a)ovirt.org&g= t;, "Ofri Masad"<br>>>>> <omasad(a)redhat.com><br>>>&= gt;> Cc: "Mike Kolesnik" <mkolesni(a)redhat.com>, "Moti Asayag"<br>&= gt;>>> <masayag(a)redhat.com>, "Oved Ourfalli" <oourfali@re= dhat.com><br>>>>> Sent: Sunday, June 30, 2013 3:59:37 PM<br>= >>>> Subject: VNIC profiles<br>>>>><br>>>>= > Hi,<br>>>>><br>>>>> We are working on adding V= NIC profiles as part of the work to add VNIC<br>>>>> QoS.<br>&g= t;>>><br>>>>> http://www.ovirt.org/Features/Network_Qo= S#VNIC_Profiles<br>>>>><br>>>>> We need to define s= ome of the system behavior followed by this change,<br>>>>> her= e is my take -<br>>>>><br>>>>> Editing a profile -<= br>>>>> --------------------<br>>>>> A user should = be able to edit the profile properties (including profile<br>>>>&g= t; name) while VMs are attached and are using this Profile (reference<br>&g= t;>>> should be done by id).<br>>>>><br>>>>&g= t; Changing the network though is a bit more tricky as long as we don't<br>= >>>> have a way to distinguish between running and current conf= igurations I<br>>>>> think it could be very confusing to the us= er. Especially since we<br>>>>> support dynamic wiring so the b= ehavior IMO is unpredictable.<br>>>>> I think it should be bloc= ked at this point.<br>>>>><br>>>>><br>>>>&= gt; Edit a VNIC / change a VNIC profile -<br>>>>> -------------= -----------------------<br>>>>> Changing the profile a VM is us= ing while the VM is running should behave<br>>>>> like dynamic = wiring (changing the VM network while it is running).<br>>>>><b= r>>>>><br>>>>> Remove a Profile -<br>>>>&g= t; -------------------<br>>>>> Is only valid if all VMs that ar= e using this profile are in status down.<br>>>>> It should upda= te all VMs to point to no profile which should behave like<br>>>>&= gt; none network today.<br>>>>><br>>>>> I see no re= ason to support a profile on a none network at this point.<br>>>>&= gt;<br>>>>> The above is also relevant for upgrade flow (upgrad= ing none network to<br>>>>> point to no profile)<br>>>&gt= ;><br>>>>><br>>>>> Removing a Network -<br>>&= gt;>> ----------------------<br>>>>> should remove all pr= ofiles on that network<br>>>>><br>>>>><br>>>&= gt;> VM snapshot/import/export -<br>>>>> -------------------= -------<br>>>>> We should handle VMs that are pointing to a net= work directly for b/w<br>>>>> compatibility.<br>>>>&gt= ; we need to select first profile that is on that network that the user<br>= >>>> has permissions on.<br>>>>><br>>>>&gt= ;<br>>>>> I assume there are more, comments are welcome<br>>= >>><br>>>>> Thanks, Livnat<br>>>>><br>>= >>><br>>><br>>><br><div><br></div></blockquote><div><b= r></div></div></body></html> ------=_Part_11407198_1454246753.1374581565910--

2 3