<DIV><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px"><BR>hi all:</SPAN></DIV>
<DIV><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px"></SPAN> </DIV>
<DIV><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px"> When I install ovirt-node, after two days I found this version by the question and I have some local storage of data on the inside, I want to upgrade ovirt-node, but I found the following error.<BR> all Hacker, please help me out a good idea...</SPAN></DIV>
<DIV><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px"><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(102,102,102); TEXT-ALIGN: justify; FONT: 12px/24px Tahoma, Arial; DISPLAY: inline !important; LETTER-SPACING: normal; TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px"></SPAN></SPAN></DIV>
<DIV><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px"></SPAN> </DIV>
<DIV><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px">[Errno 30] Read-only file system:</SPAN></DIV>
<DIV><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px">'liveos/grub'</SPAN></DIV>
<DIV><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px">Traceback(most recent call lash):</SPAN></DIV>
<DIV><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px">File</SPAN></DIV>
<DIV><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px"> "/usr/libexex/ovirt-config-installer". line 1087 in start</SPAN></DIV>
<DIV><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px"> self.upgrade_node()</SPAN></DIV>
<DIV><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px"> <SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px">File</SPAN></SPAN></DIV>
<DIV><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px"><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px"> "/usr/libexex/ovirt-config-installer". line 886, in upgrade_node()</SPAN></SPAN></DIV>
<DIV><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px"><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px"> boot_setup = install.ovirt_boot_setup()</SPAN></SPAN></DIV>
<DIV><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px"><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px">File</SPAN></SPAN></DIV>
<DIV><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px"><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px">"/usr/lib/python2.6/site-paceages/ovirtnode/install.py", line 391, in ovirt_boot_setup</SPAN></SPAN></DIV>
<DIV><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px"><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px"><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px"><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px">File</SPAN></SPAN></SPAN></SPAN></DIV>
<DIV><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px"><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px"><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px"><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px"> "/usr/lib64/python2.6/os.py", line 157 in makedirs</SPAN></SPAN></SPAN></SPAN></DIV>
<DIV><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px"><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px"><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px"><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px">OSError:[Error 30] Read-only file system:</SPAN></SPAN></SPAN></SPAN></DIV>
<DIV><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px"><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px"><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px"><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px">'/liveos/grub'</SPAN></SPAN></SPAN></SPAN></DIV>
<DIV><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px"><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px"><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px"><SPAN style="WHITE-SPACE: normal; TEXT-TRANSFORM: none; WORD-SPACING: 0px; FLOAT: none; COLOR: rgb(51,51,51); FONT: 14px/24px arial; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(251,252,254); TEXT-INDENT: 0px; -webkit-text-stroke-width: 0px"></SPAN></SPAN></SPAN></SPAN> </DIV>
<DIV>
<DIV>I at least tried mounting the LABEL=Root partition to /liveos, I was told it is busy, but I couldn't find out why it was busy, because I ran into the squashfs errors, which appeared indmesg as soon as I used tools like findmnt etc.<BR></DIV>
<DIV><BR></DIV>
<DIV style="FONT-SIZE: 12px; FONT-FAMILY: Arial Narrow; PADDING-BOTTOM: 2px; PADDING-TOP: 2px; PADDING-LEFT: 0px; PADDING-RIGHT: 0px">------------------ Original ------------------</DIV>
<DIV style="FONT-SIZE: 12px; BACKGROUND: #efefef; PADDING-BOTTOM: 8px; PADDING-TOP: 8px; PADDING-LEFT: 8px; PADDING-RIGHT: 8px">
<DIV><B>From: </B> "devel-request";<devel-request@ovirt.org>;</DIV>
<DIV><B>Date: </B> Wed, Dec 3, 2014 09:04 PM</DIV>
<DIV><B>To: </B> "devel"<devel@ovirt.org>; <WBR></DIV>
<DIV></DIV>
<DIV><B>Subject: </B> Devel Digest, Vol 9, Issue 8</DIV></DIV>
<DIV><BR></DIV>Send Devel mailing list submissions to<BR>devel@ovirt.org<BR><BR>To subscribe or unsubscribe via the World Wide Web, visit<BR>http://lists.ovirt.org/mailman/listinfo/devel<BR>or, via email, send a message with subject or body 'help' to<BR>devel-request@ovirt.org<BR><BR>You can reach the person managing the list at<BR>devel-owner@ovirt.org<BR><BR>When replying, please edit your Subject line so it is more specific<BR>than "Re: Contents of Devel digest..."<BR><BR><BR>Today's Topics:<BR><BR> 1. [QE][ACTION REQUIRED] oVirt 3.6.0 status (Sandro Bonazzola)<BR> 2. Re: ioprocess 0.14.0 released (Yeela Kaplan)<BR> 3. Re: ioprocess 0.14.0 released (Michal Skrivanek)<BR> 4. Re: Important change in UI plugins REST API integration<BR> (Yaniv Dary)<BR> 5. Re: hosted-engine setup/migration features for 3.6 (Bob Doolittle)<BR> 6. Re: hosted-engine setup/migration features for 3.6<BR> (Yedidyah Bar David)<BR><BR><BR>----------------------------------------------------------------------<BR><BR>Message: 1<BR>Date: Wed, 03 Dec 2014 10:37:19 +0100<BR>From: Sandro Bonazzola <sbonazzo@redhat.com><BR>To: "devel@ovirt.org" <devel@ovirt.org>, "Users@ovirt.org"<BR><Users@ovirt.org><BR>Subject: [ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.6.0 status<BR>Message-ID: <547ED9CF.2050408@redhat.com><BR>Content-Type: text/plain; charset=iso-8859-15<BR><BR>Hi,<BR><BR>Release criteria discussion has been closed with last week oVirt sync meeting [1].<BR><BR>Release management for 3.6.0 [2] will soon be updated with the accepted changes in release criteria.<BR>The remaining key milestones for this release must now be scheduled.<BR><BR>For reference, external project schedules we're tracking are:<BR> Fedora 21: 2014-12-09<BR> Fedora 22: 2015-XX-XX<BR> GlusterFS 3.7: 2015-04-29<BR> OpenStack Kilo: 2015-04-30<BR><BR><BR>Two different proposals have been made about above scheduling [3]:<BR>1) extend the cycle to 10 months for allowing to include a large feature set<BR>2) reduce the cycle to less than 6 months and split features over 3.6 and 3.7<BR><BR>Feature proposed for 3.6.0 must now be collected in the 3.6 Google doc [4]<BR>and reviewed by maintainers.<BR><BR>The tracker bug for 3.6.0 [5] currently shows no blockers.<BR><BR>There are 453 bugs [6] targeted to 3.6.0.<BR>Excluding node and documentation bugs we have 430 bugs [7] targeted to 3.6.0.<BR><BR><BR>[1] http://resources.ovirt.org/meetings/ovirt/2014/ovirt.2014-11-26-15.07.log.html<BR>[2] http://www.ovirt.org/OVirt_3.6_Release_Management<BR>[3] http://lists.ovirt.org/pipermail/users/2014-November/028875.html<BR>[4] http://goo.gl/9X3G49<BR>[5] https://bugzilla.redhat.com/show_bug.cgi?id=1155425<BR>[6] http://goo.gl/zwkF3r<BR>[7] http://goo.gl/ZbUiMc<BR><BR><BR>-- <BR>Sandro Bonazzola<BR>Better technology. Faster innovation. Powered by community collaboration.<BR>See how it works at redhat.com<BR><BR><BR>------------------------------<BR><BR>Message: 2<BR>Date: Wed, 3 Dec 2014 04:49:18 -0500 (EST)<BR>From: Yeela Kaplan <ykaplan@redhat.com><BR>To: Michal Skrivanek <michal.skrivanek@redhat.com><BR>Cc: Oved Ourfali <ovedo@redhat.com>, devel@ovirt.org, Martyn Taylor<BR><mtaylor@redhat.com><BR>Subject: Re: [ovirt-devel] ioprocess 0.14.0 released<BR>Message-ID:<BR><1719244357.5997272.1417600158544.JavaMail.zimbra@redhat.com><BR>Content-Type: text/plain; charset=utf-8<BR><BR><BR><BR>----- Original Message -----<BR>> From: "Michal Skrivanek" <michal.skrivanek@redhat.com><BR>> To: "Saggi Mizrahi" <smizrahi@redhat.com>, "Oved Ourfali" <ovedo@redhat.com><BR>> Cc: "Martyn Taylor" <mtaylor@redhat.com>, devel@ovirt.org<BR>> Sent: Wednesday, December 3, 2014 11:30:34 AM<BR>> Subject: Re: [ovirt-devel] ioprocess 0.14.0 released<BR>> <BR>> <BR>> On Oct 23, 2014, at 10:06 , Saggi Mizrahi <smizrahi@redhat.com> wrote:<BR>> <BR>> > <BR>> > <BR>> > ----- Original Message -----<BR>> >> From: "Michal Skrivanek" <michal.skrivanek@redhat.com><BR>> >> To: "Saggi Mizrahi" <smizrahi@redhat.com><BR>> >> Cc: devel@ovirt.org, "Martyn Taylor" <mtaylor@redhat.com><BR>> >> Sent: Wednesday, October 22, 2014 10:55:34 AM<BR>> >> Subject: Re: [ovirt-devel] ioprocess 0.14.0 released<BR>> >> <BR>> >> <BR>> >> On Oct 21, 2014, at 10:59 , Saggi Mizrahi <smizrahi@redhat.com> wrote:<BR>> >> <BR>> >>> ioprocess 0.14.0 has been tagged and released.<BR>> >>> <BR>> >>> The changelog includes:<BR>> >>> - python-bindings: IOProcess objects can be collected by the GC<BR>> >>> - python-bindings: Slave processes can optionally be collected<BR>> >>> by zombie reaper<BR>> >>> <BR>> >>> It's recommended that everyone upgrade to the latest version.<BR>> >> <BR>> >> does this remove the annoying debug level messages in vdsm.log?<BR>> >> or some other patch already addressed that?<BR>> > Long long time ago. We added the TRACE level that is only<BR>> > used during iprocess development.<BR>> > <BR>> > * Sun Jul 20 2014 Saggi Mizrahi <smizrahi@redhat.com> 0.6.1-1<BR>> > - Reduced logging even for debug level<BR>> <BR>> well, I still see that in *latest* 3.5 on QE systems. It's really annoying?<BR>> might it be because of upgrades?<BR>> Oved, IMHO it needs to be fixed/clarified ASAP, the logs are useless...<BR>> <BR><BR>If QE has latest 3.5 then they should have ioprocess-0.14 installed,<BR>if that's the case and there's still too much logging then the issue should be checked.<BR><BR>> Thanks,<BR>> michal<BR>> <BR>> >> <BR>> >> Thanks,<BR>> >> michal<BR>> >> <BR>> >>> <BR>> >>> Please test and give karma:<BR>> >>> https://admin.fedoraproject.org/updates/search/ioprocess-0.14.0<BR>> >>> <BR>> >>> Good day.<BR>> >>> _______________________________________________<BR>> >>> Devel mailing list<BR>> >>> Devel@ovirt.org<BR>> >>> http://lists.ovirt.org/mailman/listinfo/devel<BR>> >> <BR>> >> <BR>> <BR>> _______________________________________________<BR>> Devel mailing list<BR>> Devel@ovirt.org<BR>> http://lists.ovirt.org/mailman/listinfo/devel<BR>> <BR><BR><BR>------------------------------<BR><BR>Message: 3<BR>Date: Wed, 3 Dec 2014 10:57:33 +0100<BR>From: Michal Skrivanek <michal.skrivanek@redhat.com><BR>To: Yeela Kaplan <ykaplan@redhat.com><BR>Cc: Oved Ourfali <ovedo@redhat.com>, devel@ovirt.org, Martyn Taylor<BR><mtaylor@redhat.com><BR>Subject: Re: [ovirt-devel] ioprocess 0.14.0 released<BR>Message-ID: <746EE06D-1C7C-46C3-8432-0949536C7544@redhat.com><BR>Content-Type: text/plain; charset=windows-1252<BR><BR><BR>On Dec 3, 2014, at 10:49 , Yeela Kaplan <ykaplan@redhat.com> wrote:<BR><BR>> <BR>> <BR>> ----- Original Message -----<BR>>> From: "Michal Skrivanek" <michal.skrivanek@redhat.com><BR>>> To: "Saggi Mizrahi" <smizrahi@redhat.com>, "Oved Ourfali" <ovedo@redhat.com><BR>>> Cc: "Martyn Taylor" <mtaylor@redhat.com>, devel@ovirt.org<BR>>> Sent: Wednesday, December 3, 2014 11:30:34 AM<BR>>> Subject: Re: [ovirt-devel] ioprocess 0.14.0 released<BR>>> <BR>>> <BR>>> On Oct 23, 2014, at 10:06 , Saggi Mizrahi <smizrahi@redhat.com> wrote:<BR>>> <BR>>>> <BR>>>> <BR>>>> ----- Original Message -----<BR>>>>> From: "Michal Skrivanek" <michal.skrivanek@redhat.com><BR>>>>> To: "Saggi Mizrahi" <smizrahi@redhat.com><BR>>>>> Cc: devel@ovirt.org, "Martyn Taylor" <mtaylor@redhat.com><BR>>>>> Sent: Wednesday, October 22, 2014 10:55:34 AM<BR>>>>> Subject: Re: [ovirt-devel] ioprocess 0.14.0 released<BR>>>>> <BR>>>>> <BR>>>>> On Oct 21, 2014, at 10:59 , Saggi Mizrahi <smizrahi@redhat.com> wrote:<BR>>>>> <BR>>>>>> ioprocess 0.14.0 has been tagged and released.<BR>>>>>> <BR>>>>>> The changelog includes:<BR>>>>>> - python-bindings: IOProcess objects can be collected by the GC<BR>>>>>> - python-bindings: Slave processes can optionally be collected<BR>>>>>> by zombie reaper<BR>>>>>> <BR>>>>>> It's recommended that everyone upgrade to the latest version.<BR>>>>> <BR>>>>> does this remove the annoying debug level messages in vdsm.log?<BR>>>>> or some other patch already addressed that?<BR>>>> Long long time ago. We added the TRACE level that is only<BR>>>> used during iprocess development.<BR>>>> <BR>>>> * Sun Jul 20 2014 Saggi Mizrahi <smizrahi@redhat.com> 0.6.1-1<BR>>>> - Reduced logging even for debug level<BR>>> <BR>>> well, I still see that in *latest* 3.5 on QE systems. It's really annoying?<BR>>> might it be because of upgrades?<BR>>> Oved, IMHO it needs to be fixed/clarified ASAP, the logs are useless...<BR>>> <BR>> <BR>> If QE has latest 3.5 then they should have ioprocess-0.14 installed,<BR>> if that's the case and there's still too much logging then the issue should be checked.<BR><BR>Ha! indeed it was not the case. The system as somehow missing many updates, including ioprocess.<BR>It should have probably been enforced?but I agree if one does a proper yum update it should work (I didn't try it yet;-)<BR><BR>Thanks,<BR>michal<BR><BR>> <BR>>> Thanks,<BR>>> michal<BR>>> <BR>>>>> <BR>>>>> Thanks,<BR>>>>> michal<BR>>>>> <BR>>>>>> <BR>>>>>> Please test and give karma:<BR>>>>>> https://admin.fedoraproject.org/updates/search/ioprocess-0.14.0<BR>>>>>> <BR>>>>>> Good day.<BR>>>>>> _______________________________________________<BR>>>>>> Devel mailing list<BR>>>>>> Devel@ovirt.org<BR>>>>>> http://lists.ovirt.org/mailman/listinfo/devel<BR>>>>> <BR>>>>> <BR>>> <BR>>> _______________________________________________<BR>>> Devel mailing list<BR>>> Devel@ovirt.org<BR>>> http://lists.ovirt.org/mailman/listinfo/devel<BR>>> <BR><BR><BR><BR>------------------------------<BR><BR>Message: 4<BR>Date: Wed, 3 Dec 2014 05:02:19 -0500 (EST)<BR>From: Yaniv Dary <ydary@redhat.com><BR>To: Vojtech Szocs <vszocs@redhat.com><BR>Cc: devel@ovirt.org<BR>Subject: Re: [ovirt-devel] Important change in UI plugins REST API<BR>integration<BR>Message-ID:<BR><1781152095.22179849.1417600939871.JavaMail.zimbra@redhat.com><BR>Content-Type: text/plain; charset=utf-8<BR><BR>Does this affect any 3rd parties that implemented UI plugins?<BR>Will they need to change anything or is this change more a behaviour change only?<BR><BR><BR><BR>Yaniv<BR><BR>----- Original Message -----<BR>> From: "Vojtech Szocs" <vszocs@redhat.com><BR>> To: "Alon Bar-Lev" <alonbl@redhat.com><BR>> Cc: devel@ovirt.org<BR>> Sent: Tuesday, December 2, 2014 7:12:21 PM<BR>> Subject: Re: [ovirt-devel] Important change in UI plugins REST API integration<BR>> <BR>> <BR>> <BR>> ----- Original Message -----<BR>> > From: "Alon Bar-Lev" <alonbl@redhat.com><BR>> > To: "Sven Kieske" <s.kieske@mittwald.de><BR>> > Cc: devel@ovirt.org<BR>> > Sent: Tuesday, December 2, 2014 9:43:18 AM<BR>> > Subject: Re: [ovirt-devel] Important change in UI plugins REST API<BR>> > integration<BR>> > <BR>> > <BR>> > <BR>> > ----- Original Message -----<BR>> > > From: "Sven Kieske" <s.kieske@mittwald.de><BR>> > > To: devel@ovirt.org<BR>> > > Sent: Tuesday, December 2, 2014 10:41:00 AM<BR>> > > Subject: Re: [ovirt-devel] Important change in UI plugins REST API<BR>> > > integration<BR>> > > <BR>> > > <BR>> > > <BR>> > > On 01/12/14 20:26, Vojtech Szocs wrote:<BR>> > > > In other words, usability of REST session ID is now strictly<BR>> > > > scoped to GUI user being authenticated. If the user logs in,<BR>> > > > (always) new REST session ID will be passed to all UI plugins.<BR>> > > > If the user logs out, REST session ID will not work anymore.<BR>> > > <BR>> > > What if I use just REST for logging in and doing something<BR>> > > without any GUI interaction at all?<BR>> <BR>> This announcement was about UI plugins in WebAdmin. If you use<BR>> Engine REST API without any GUI interaction involved, you aren't<BR>> affected in any way.<BR>> <BR>> > > <BR>> > > this reads a little like: you always need an open web gui<BR>> > > to be able to use REST, which does not make sense at all.<BR>> <BR>> Sorry if my email confused you. It should read like: if you're<BR>> an author of oVirt UI plugin for WebAdmin, please beware that<BR>> REST API session ID (automatically acquired by UI plugin infra<BR>> on behalf of all UI plugins) will not work after GUI logout.<BR>> <BR>> > <BR>> > If you provide your own credentials nothing changed.<BR>> > <BR>> > The change is only effecting RESTAPI usage within the user interface using<BR>> > the credentials obtained interactively from the user within login page.<BR>> > <BR>> > > So I guess I'm misreading this?<BR>> > > <BR>> > > --<BR>> > > Mit freundlichen Gr??en / Regards<BR>> > > <BR>> > > Sven Kieske<BR>> > > <BR>> > > Systemadministrator<BR>> > > Mittwald CM Service GmbH & Co. KG<BR>> > > K?nigsberger Stra?e 6<BR>> > > 32339 Espelkamp<BR>> > > T: +49-5772-293-100<BR>> > > F: +49-5772-293-333<BR>> > > https://www.mittwald.de<BR>> > > Gesch?ftsf?hrer: Robert Meyer<BR>> > > St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad<BR>> > > Oeynhausen<BR>> > > Komplement?rin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad<BR>> > > Oeynhausen<BR>> > > _______________________________________________<BR>> > > Devel mailing list<BR>> > > Devel@ovirt.org<BR>> > > http://lists.ovirt.org/mailman/listinfo/devel<BR>> > _______________________________________________<BR>> > Devel mailing list<BR>> > Devel@ovirt.org<BR>> > http://lists.ovirt.org/mailman/listinfo/devel<BR>> _______________________________________________<BR>> Devel mailing list<BR>> Devel@ovirt.org<BR>> http://lists.ovirt.org/mailman/listinfo/devel<BR><BR><BR>------------------------------<BR><BR>Message: 5<BR>Date: Wed, 3 Dec 2014 07:53:24 -0500<BR>From: Bob Doolittle <bob@doolittle.us.com><BR>To: Yedidyah Bar David <didi@redhat.com><BR>Cc: users-ovirt <users@ovirt.org>, "devel@ovirt.org" <devel@ovirt.org><BR>Subject: Re: [ovirt-devel] hosted-engine setup/migration features for<BR>3.6<BR>Message-ID:<BR><CA+4jJ+szppQQuPTBgCW+v0s2rcVgBzamLQoYnnqAG5xR5gLarg@mail.gmail.com><BR>Content-Type: text/plain; charset="utf-8"<BR><BR>Resending - inadvertently dropped CCs.<BR><BR>On Wed, Dec 3, 2014 at 7:50 AM, Bob Doolittle <bob@doolittle.us.com> wrote:<BR><BR>> Another issue with that page is that it assumes a remote database. I am<BR>> not sure what percentage of cases have remote databases but clearly many<BR>> (most?) do not, since that's not default behavior. So that page definitely<BR>> needs attention. See:<BR>> https://bugzilla.redhat.com/show_bug.cgi?id=1099995<BR>> https://bugzilla.redhat.com/show_bug.cgi?id=1099998<BR>><BR>> Some of us have wanted to disable global maintenance upon bootup by adding<BR>> a systemd service on Fedora 20 (since you must enable global maintenance to<BR>> shut it down cleanly), and have found it impossible to create the necessary<BR>> systemd dependencies. It seems that (at least with 3.4) hosted-engine<BR>> --set-maintenance --mode=none will return an error for several seconds<BR>> after all other services have started and it's not clear what can be waited<BR>> upon in order to issue the command with assurance it will complete<BR>> successfully. This isn't strictly a setup/migration issue but it is an<BR>> issue with setting up a desired configuration with hosted-engine. The way<BR>> to reproduce this is simply to wait until gdm-greeter displays the login<BR>> prompt, ssh into the system and execute hosted-engine --set-maintenance<BR>> --mode=none and observe the error. Or create a systemd service that depends<BR>> upon (waits for) the latest-possible service, try executing the command<BR>> there, and observe the error. Ideally there would be some external<BR>> observable event which a systemd service could depend upon, when<BR>> hosted-engine is ready to do its thing.<BR>><BR>> Regards,<BR>> Bob<BR>><BR>><BR>> On Wed, Dec 3, 2014 at 2:59 AM, Yedidyah Bar David <didi@redhat.com><BR>> wrote:<BR>><BR>>> Hi all,<BR>>><BR>>> We already have quite a lot of open ovirt-hosted-engine-setup bugs for<BR>>> 3.6 [1].<BR>>><BR>>> Yesterday I tried helping someone on irc who planned to migrate to<BR>>> hosted-engine<BR>>> manually, and without knowing (so it seems) that such a feature exists.<BR>>> He had<BR>>> an engine set up on a physical host, prepared a VM for it, and asked<BR>>> about migrating<BR>>> the engine to the VM. In principle this works, but the final result will<BR>>> be a<BR>>> hosted-engine, where the engine manages a VM the runs itself, without<BR>>> knowing it,<BR>>> and without HA.<BR>>><BR>>> The current recommended migration flow is described in [2]. This page is<BR>>> perhaps<BR>>> a bit outdated, perhaps missing some details etc., but principally works.<BR>>> The main<BR>>> issue with it, AFAICT after discussing this a bit with few people, is<BR>>> that it<BR>>> requires a new clean host.<BR>>><BR>>> I'd like to hear what people here think about such and similar flows.<BR>>><BR>>> If you already had an engine and migrated to hosted-engine, what was<BR>>> good, what<BR>>> was bad, what would you like to change?<BR>>><BR>>> If you plan such a migration, what do you find missing currently?<BR>>><BR>>> [1] http://red.ht/1vle8Vv<BR>>> [2] http://www.ovirt.org/Migrate_to_Hosted_Engine<BR>>><BR>>> Best,<BR>>> --<BR>>> Didi<BR>>> _______________________________________________<BR>>> Devel mailing list<BR>>> Devel@ovirt.org<BR>>> http://lists.ovirt.org/mailman/listinfo/devel<BR>>><BR>><BR>><BR>-------------- next part --------------<BR>An HTML attachment was scrubbed...<BR>URL: <http://lists.ovirt.org/pipermail/devel/attachments/20141203/d8ab2364/attachment-0001.html><BR><BR>------------------------------<BR><BR>Message: 6<BR>Date: Wed, 3 Dec 2014 08:04:17 -0500 (EST)<BR>From: Yedidyah Bar David <didi@redhat.com><BR>To: Bob Doolittle <bob@doolittle.us.com><BR>Cc: users <users@ovirt.org>, devel <devel@ovirt.org><BR>Subject: Re: [ovirt-devel] hosted-engine setup/migration features for<BR>3.6<BR>Message-ID:<BR><1810755665.22244497.1417611857805.JavaMail.zimbra@redhat.com><BR>Content-Type: text/plain; charset=utf-8<BR><BR>----- Original Message -----<BR>> From: "Bob Doolittle" <bob@doolittle.us.com><BR>> To: "Yedidyah Bar David" <didi@redhat.com><BR>> Sent: Wednesday, December 3, 2014 2:50:12 PM<BR>> Subject: Re: [ovirt-devel] hosted-engine setup/migration features for 3.6<BR>> <BR>> Another issue with that page is that it assumes a remote database. I am not<BR>> sure what percentage of cases have remote databases but clearly many<BR>> (most?) do not, since that's not default behavior.<BR><BR>I agree.<BR><BR>> So that page definitely<BR>> needs attention. See:<BR>> https://bugzilla.redhat.com/show_bug.cgi?id=1099995<BR><BR>Indeed. Note that this isn't specific to hosted-engine, it's the same for<BR>any migration using engine-backup to backup/restore, therefore there is<BR>a link to its page in the top, where this is more detailed. We also have<BR>a bug [3] to automate this.<BR><BR>[3] https://bugzilla.redhat.com/show_bug.cgi?id=1064503<BR><BR>> https://bugzilla.redhat.com/show_bug.cgi?id=1099998<BR>> <BR>> Some of us have wanted to disable global maintenance upon bootup by adding<BR>> a systemd service on Fedora 20 (since you must enable global maintenance to<BR>> shut it down cleanly), and have found it impossible to create the necessary<BR>> systemd dependencies. It seems that (at least with 3.4) hosted-engine<BR>> --set-maintenance --mode=none will return an error for several seconds<BR>> after all other services have started and it's not clear what can be waited<BR>> upon in order to issue the command with assurance it will complete<BR>> successfully. This isn't strictly a setup/migration issue but it is an<BR>> issue with setting up a desired configuration with hosted-engine. The way<BR>> to reproduce this is simply to wait until gdm-greeter displays the login<BR>> prompt, ssh into the system and execute hosted-engine --set-maintenance<BR>> --mode=none and observe the error. Or create a systemd service that depends<BR>> upon (waits for) the latest-possible service, try executing the command<BR>> there, and observe the error. Ideally there would be some external<BR>> observable event which a systemd service could depend upon, when<BR>> hosted-engine is ready to do its thing.<BR><BR>Adding Jiri for that. Do you have an open bug?<BR><BR>Thanks,<BR><BR>> <BR>> Regards,<BR>> Bob<BR>> <BR>> <BR>> On Wed, Dec 3, 2014 at 2:59 AM, Yedidyah Bar David <didi@redhat.com> wrote:<BR>> <BR>> > Hi all,<BR>> ><BR>> > We already have quite a lot of open ovirt-hosted-engine-setup bugs for 3.6<BR>> > [1].<BR>> ><BR>> > Yesterday I tried helping someone on irc who planned to migrate to<BR>> > hosted-engine<BR>> > manually, and without knowing (so it seems) that such a feature exists. He<BR>> > had<BR>> > an engine set up on a physical host, prepared a VM for it, and asked about<BR>> > migrating<BR>> > the engine to the VM. In principle this works, but the final result will<BR>> > be a<BR>> > hosted-engine, where the engine manages a VM the runs itself, without<BR>> > knowing it,<BR>> > and without HA.<BR>> ><BR>> > The current recommended migration flow is described in [2]. This page is<BR>> > perhaps<BR>> > a bit outdated, perhaps missing some details etc., but principally works.<BR>> > The main<BR>> > issue with it, AFAICT after discussing this a bit with few people, is that<BR>> > it<BR>> > requires a new clean host.<BR>> ><BR>> > I'd like to hear what people here think about such and similar flows.<BR>> ><BR>> > If you already had an engine and migrated to hosted-engine, what was good,<BR>> > what<BR>> > was bad, what would you like to change?<BR>> ><BR>> > If you plan such a migration, what do you find missing currently?<BR>> ><BR>> > [1] http://red.ht/1vle8Vv<BR>> > [2] http://www.ovirt.org/Migrate_to_Hosted_Engine<BR>> ><BR>> > Best,<BR>> > --<BR>> > Didi<BR>> > _______________________________________________<BR>> > Devel mailing list<BR>> > Devel@ovirt.org<BR>> > http://lists.ovirt.org/mailman/listinfo/devel<BR>> ><BR>> <BR><BR>-- <BR>Didi<BR><BR><BR><BR>------------------------------<BR><BR>_______________________________________________<BR>Devel mailing list<BR>Devel@ovirt.org<BR>http://lists.ovirt.org/mailman/listinfo/devel<BR><BR>End of Devel Digest, Vol 9, Issue 8<BR>***********************************
<DIV></DIV></DIV>