- Devel - oVirt List Archives

[ANN] oVirt 3.5.0 Third Release Candidate is now available for testing
by Sandro Bonazzola 24 Sep '14

24 Sep '14

The oVirt team is pleased to announce that the 3.5.0 Third Release Candidate is now available for testing as of Sep 24th 2014. The release candidate is available now for Fedora 19, Fedora 20 and Red Hat Enterprise Linux 6.5 (or similar) and allow you to use Red Hat Enterprise Linux 7 as node and run Hosted Engine. This release of oVirt includes numerous bug fixes. See the release notes [1] for a list of the new features and bugs fixed. The existing repository ovirt-3.5-pre has been updated for delivering this release without the need of enabling any other repository. If you're already using oVirt 3.5 repository, please update ovirt-release35 rpm. Please refer to release notes [1] for Installation / Upgrade instructions. New oVirt Live, oVirt Guest Tools and oVirt Node ISO will be available soon as well[2]. Please note that mirrors may need usually one day before being synchronized. If you want to be sure to use latest rpms and don't want to wait for the mirrors, you can edit /etc/yum.repos.d/ovirt-3.5.repo commenting the mirror line and removing the comment on baseurl line. Please refer to the release notes for known issues in this release. [1] http://www.ovirt.org/OVirt_3.5_Release_Notes [2] http://resources.ovirt.org/pub/ovirt-3.5-pre/iso/ -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

oVirt 3.4 entering security/critical fix only phase
by Sandro Bonazzola 24 Sep '14

24 Sep '14

Hi, As you should know, we released oVirt 3.4.4 yesterday. After this release, only security/critical fixes will be allowed on 3.4 branch and only a security/critical update will cause a new oVirt 3.4.z release. It's time to focus on new features for 3.6.0! Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Packages for oVirt 3.5.0 RC3
by Sandro Bonazzola 24 Sep '14

24 Sep '14

# From developers: # Log Collector http://jenkins.ovirt.org/job/manual-build-tarball/412/ # ISO Uploader http://jenkins.ovirt.org/job/manual-build-tarball/411/ # Image Uploader http://jenkins.ovirt.org/job/manual-build-tarball/410/ # Hosted Engine http://jenkins.ovirt.org/job/ovirt-hosted-engine-ha_any_create-rpms_manual/… http://jenkins.ovirt.org/job/ovirt-hosted-engine-setup_any_create-rpms_manu… # VDSM # F20 http://koji.fedoraproject.org/koji/taskinfo?taskID=7648992 # F19 http://koji.fedoraproject.org/koji/taskinfo?taskID=7649080 # rhel6 http://koji.fedoraproject.org/koji/taskinfo?taskID=7649142 #rhel7 http://koji.fedoraproject.org/koji/taskinfo?taskID=7649251 #rhel7 ppc64 http://koji.fedoraproject.org/koji/taskinfo?taskID=7649263 # Delivered by Fedora / EPEL: # - ioprocess # - mom # Remaining packages will be taken from Jenkins 3.5 Publisher once pending patches for the engine will be merged and engine built. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 4

Fedora 21 Test Day
by Federico Simoncelli 23 Sep '14

23 Sep '14

FYI, in a couple of days it will be the Fedora 21 virtualization test day: http://fedoramagazine.org/5tftw-2014-09-02/ https://fedoraproject.org/wiki/Test_Day:2014-09-25_Virtualization it's a good opportunity for us to check for regressions with vdsm (qemu, libvirt, virt-tools), get more attention from the fedora community, have quicker feedback on issues and get them fixed before release. -- Federico

2 1

vdsm 3.5 rpm build is failing
by Piotr Kliczewski 23 Sep '14

23 Sep '14

All, I noticed that vdsm rpm build is failing: http://jenkins-ci.eng.lab.tlv.redhat.com/job/vdsm_3.5_rpm_factory/779/artif… Thanks, Piotr

2 2

Re: [ovirt-devel] oVirt Node weekly meeting
by Fabian Deutsch 23 Sep '14

23 Sep '14

Moving this out a week, so everybody can attend. Let me know if the new time works for all of you. Thanks fabian ----- Original Message ----- > The following meeting has been modified: > > Subject: oVirt Node weekly meeting > Organiser: "Fabian Deutsch" <fdeutsch(a)redhat.com> > > Location: irc://irc.oftc.net#ovirt > Time: 3:00:00 PM - 3:30:00 PM GMT +01:00 Amsterdam, Berlin, Bern, Rome, > Stockholm, Vienna [MODIFIED] > Recurrence : Every Tuesday No end date Effective 15 Oct, 2013 > > Invitees: devel(a)ovirt.org > > > *~*~*~*~*~*~*~*~*~* > > Hey, > > this is an invitation to the weekly oVirt Node devel meetings. > Anyone interested or related to Node development is welcome.

1 0

Fwd: Re: Geo-replication user flows
by Sahina Bose 23 Sep '14

23 Sep '14

This is a multi-part message in MIME format. --------------070706000003030108020808 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit FYI... Feedback about geo-replication user flows - thanks to Ju. (http://www.ovirt.org/Features/Gluster_Geo_Replication#User_Experience) Please feel free to add/comment thanks sahina -------- Original Message -------- Subject: Re: Geo-replication user flows Date: Tue, 16 Sep 2014 13:49:17 -0400 From: Ju Lim <julim(a)redhat.com> To: Sahina Bose <sabose(a)redhat.com> Hi Sahina: Thanks for getting back to me. I took away 3 action items from the email: Geo-replication session configuration options mockup -- we're working on putting something together Dashboard - what to show in the dashboard; we're working on putting something together Checkpoint history - what to show. Here's what I believe you should show: * show what you would get from the "# gluster volume geo-replication <source_volume> <destination_host>::<destination_volume> config log-file | xargs grep checkpoint" command * show the following columns (I'll assume you don't need a mockup as this most likely would be shown in a table) o checkpoint name, checkpoint creation date, amount of data transferred (indicate if delta or cumulative size), status Please feel free to forward to oVirt users. Thanks, Ju On Sep 12, 2014, at 5:01 AM, Sahina Bose <sabose(a)redhat.com <mailto:sabose@redhat.com>> wrote: > Ju, > > Thanks for the detailed feedback. My responses inline. > > On 09/11/2014 01:24 AM, Ju Lim wrote: >> Sahina: >> >> I finally had some time to review the Geo-replication proposal on >> http://www.ovirt.org/Features/Gluster_Geo_Replication#User_Experience. >> >> Will we have a tab (sibling to Volumes, Clusters, etc.) for >> Replication Sessions so a user can see all Geo-Replication Sessions >> in 1 place vs. looking into every volume to identify them? I see >> later a question asked about it. +1 that we need a "Geo-Replication >> Sessions" or "Geo-Replication" in the main tab. > > This tab would be empty if there are no replication sessions. > But having a tab will all replication sessions would be useful and > could be used to start a new one. > > >> >> Is there a proposal yet for what we'll show related to replication in >> the dashboard? > > No, no proposal yet. > >> >> For the Geo-Replication detail tab (in the Volume main tab), >> Should the action be "New" or "Create Session"? Reason I ask is that >> it's "Create Volume" vs. "New Volume" in the master area. > > We are trying to be consistent with the verbs..and have changed to > Volume -> New for creating a volume. So it should be "New Session" IMO > > >> >> For the Create Session / New, can we use the same dialog whether it's >> coming from the Geo-Replication detail tab (in the Volume main tab) >> and the "Geo-Replication Sessions" main tab? >> >> The only difference is that the one from the main tab would >> additionally ask the source (host / IP Address + volume). For the >> detail tab, instead of prompting for the source, we can show it. > > Yes, it can be the same dialog. The information regarding source > volume would be prefilled if it's coming from the geo-replication sub-tab. > > >> >> For the Destination (or Remote) Cluster Volumes, can the destination >> volume be of a different volume type to participate in geo-replication? > > Destination volume can be of a different volume type. > >> >> For the Geo-Replication Session Options, can we make the >> configuration options >> (https://access.redhat.com/documentation/en-US/Red_Hat_Storage/2.1/html/Admi…) more >> usable vs. cryptic as it currently seems? Specifically, can we >> showcase the defaults and provide the rest as Advanced configurations >> that they can change? > > We were planning to have a UI similar to the volume options. Do let us > know, if there's a better way to do this. > >> >> The Geo-Replication Session Details view -- I'm not sure what this is >> telling the user other then how long the host has been up. Does this >> mean that replication has been running for as long as the uptime for >> those hosts? It seems to be missing Checkpoint information and >> Checkpoint history information, which is important for >> geo-replication consistency. >> >> Specifically, when I think of what is typically shown in a >> geo-replication session, I'd expect to see the following columns of >> information: >> >> Source Volume, Destination / Remote Volume, Status, Last Checkpoint, >> Last Checkpoint Label >> >> If different volume types can be used within the same replication >> session, then we would also want to show the volume type on the >> remote volume. > > Session details view will also show information on files/bytes > skipped, moved etc per brick node. > > Regarding checkpoint, there's currently only a checkpoint status being > shown. There's some enhancements to be done in gluster geo-rep with > regards to checkpoints > > What information would need to be shown in checkpoint history? > > >> >> BTW, do you know if there are plans to show volume size (total, used, >> available/remaining) in the Volume master area? > > Yes, we have introduced a volume capacity column in the Volumes tab, > which will show these details. > >> >> Is there any possibility to change the terminology from master-slave >> to source-destination, source-remote, master-remote? The >> master-slave terminology is quite unusual in the storage replication >> realm. I ask as I see docs, CLI, etc. that already use the >> master-slave terminology. > > We could change in the docs and UI...CLI, not so sure. > > >> >> We're happy to put together mockups and/or a proposal if it would be >> helpful. Is this the best way to provide input, or should I be >> posting my comments on >> http://www.ovirt.org/Talk:Features/Gluster_Geo_Replication? > > If you have suggestions on showing the configuration options and for > the dashboard, that would be welcome. > I could forward this to ovirt users for wider circulation. > > thanks! > >> >> Please advise. >> >> Thanks, >> Ju >> >> >> On Sep 4, 2014, at 10:23 AM, Sahina Bose <sabose(a)redhat.com >> <mailto:sabose@redhat.com>> wrote: >> >>> Hi all, >>> >>> The user experience section >>> http://www.ovirt.org/Features/Gluster_Geo_Replication#User_Experience , >>> has been updated to capture the user flows. (The mockups, however, >>> are older and do not completely reflect the updated text) >>> >>> There are couple of open questions. Please review and provide >>> suggestions. >>> >>> thanks >>> sahina >>> >> > --------------070706000003030108020808 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"> FYI... Feedback about geo-replication user flows - thanks to Ju. (<a class="moz-txt-link-freetext" href="http://www.ovirt.org/Features/Gluster_Geo_Replication#User_Experience">http://www.ovirt.org/Features/Gluster_Geo_Replication#User_Experience</a>).<br> <br> Please feel free to add/comment<br> <br> thanks<br> sahina<br> <div class="moz-forward-container"><br> <br> -------- Original Message -------- <table class="moz-email-headers-table" cellpadding="0" cellspacing="0" border="0"> <tbody> <tr> <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject: </th> <td>Re: Geo-replication user flows</td> </tr> <tr> <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th> <td>Tue, 16 Sep 2014 13:49:17 -0400</td> </tr> <tr> <th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th> <td>Ju Lim <a class="moz-txt-link-rfc2396E" href="mailto:julim@redhat.com"><julim(a)redhat.com></a></td> </tr> <tr> <th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th> <td>Sahina Bose <a class="moz-txt-link-rfc2396E" href="mailto:sabose@redhat.com"><sabose(a)redhat.com></a></td> </tr> <tr> <th align="RIGHT" nowrap="nowrap" valign="BASELINE"><br> </th> <td><br> </td> </tr> </tbody> </table> <br> <br> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> Hi Sahina: <div><br> </div> <div>Thanks for getting back to me.  I took away 3 action items from the email:</div> <div><br> </div> <div> <div> <div><font face="Arial">Geo-replication session configuration options mockup -- we're working on putting something together</font></div> <div><font face="Arial"><br> </font></div> <div> <div><font face="Arial">Dashboard - what to show in the dashboard; </font><span style="font-family: Arial; ">we're working on putting something together</span></div> </div> </div> <div><span style="font-family: Arial; "><br> </span></div> <div> <div><font face="Arial">Checkpoint history - what to show.  Here's what I believe you should show:</font></div> <div> <ul> <li><font face="Arial">show what you would get from the "<span style="background-color: rgb(245, 245, 245); line-height: 18.2000007629395px; orphans: 4; text-align: left; white-space: pre-wrap; widows: 4; "># gluster volume geo-replication <source_volume> <destination_host>::<destination_volume> config log-file | xargs grep checkpoint" command</span></font></li> <li><span style="background-color: rgb(245, 245, 245); line-height: 18.2000007629395px; orphans: 4; text-align: left; white-space: pre-wrap; widows: 4; "><font face="Arial">show the following columns (I'll assume you don't need a mockup as this most likely would be shown in a table)</font></span></li> <ul> <li><span style="background-color: rgb(245, 245, 245); line-height: 18.2000007629395px; orphans: 4; text-align: left; white-space: pre-wrap; widows: 4; "><font face="Arial">checkpoint name, checkpoint creation date, amount of data transferred (indicate if delta or cumulative size), status</font></span></li> </ul> </ul> <div>Please feel free to forward to oVirt users.</div> </div> </div> </div> <div><br> </div> <div>Thanks,</div> <div>Ju</div> <div><br> </div> <div> <div> <div>On Sep 12, 2014, at 5:01 AM, Sahina Bose <<a moz-do-not-send="true" href="mailto:sabose@redhat.com">sabose(a)redhat.com</a>> wrote:</div> <br class="Apple-interchange-newline"> <blockquote type="cite"> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> <div bgcolor="#FFFFFF" text="#000000"> Ju,<br> <br> Thanks for the detailed feedback. My responses inline.<br> <br> <div class="moz-cite-prefix">On 09/11/2014 01:24 AM, Ju Lim wrote:<br> </div> <blockquote cite="mid:EDB5A6A7-C6ED-4A4A-A15C-5405FF771F92@redhat.com" type="cite"> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> <span style="line-height: 22px; font-size: 13px;"><font face="Arial">Sahina:</font></span> <div><font style="font-size: 13px;" face="Arial"><br> </font></div> <div><font style="font-size: 13px;" face="Arial">I finally had some time to review the Geo-replication proposal on <a moz-do-not-send="true" href="http://www.ovirt.org/Features/Gluster_Geo_Replication#User_Experience" style="line-height: 15px; ">http://www.ovirt.org/Features/Gluster_Geo_Replication#User_Experience</a>.</font></div> <div><font style="font-size: 13px;" face="Arial"><br> </font></div> <div><font style="font-size: 13px;" face="Arial">Will we have a tab (sibling to Volumes, Clusters, etc.) for Replication Sessions so a user can see all Geo-Replication Sessions in 1 place vs. looking into every volume to identify them?  I see later a question asked about it.  +1 that we need a "Geo-Replication Sessions" or "Geo-Replication" in the main tab.</font></div> </blockquote> <br> <font face="Arial">This tab would be empty if there are no replication sessions.<br> But having a tab will all replication sessions would be useful and could be used to start a new one.<br> <br>  <br> </font> <blockquote cite="mid:EDB5A6A7-C6ED-4A4A-A15C-5405FF771F92@redhat.com" type="cite"> <div><font style="font-size: 13px;" face="Arial"><br> </font></div> <div><font style="font-size: 13px;" face="Arial">Is there a proposal yet for what we'll show related to replication in the dashboard?</font></div> </blockquote> <br> <font face="Arial">No, no proposal yet.<br> <br> </font> <blockquote cite="mid:EDB5A6A7-C6ED-4A4A-A15C-5405FF771F92@redhat.com" type="cite"> <div><font style="font-size: 13px;" face="Arial"><br> </font></div> <div><font style="font-size: 13px;" face="Arial">For the Geo-Replication detail tab (in the Volume main tab), </font></div> <div><font style="font-size: 13px;" face="Arial">Should the action be "New" or "Create Session"?  Reason I ask is that it's "Create Volume" vs. "New Volume" in the master area.</font></div> </blockquote> <br> We are trying to be consistent with the verbs..and have changed to Volume -> New for creating a volume. So it should be "New Session" IMO<br> <br> <br> <blockquote cite="mid:EDB5A6A7-C6ED-4A4A-A15C-5405FF771F92@redhat.com" type="cite"> <div><font style="font-size: 13px;" face="Arial"><br> </font></div> <div><font style="font-size: 13px;" face="Arial">For the Create Session / New, can we use the same dialog whether it's coming from the Geo-Replication detail tab (in the Volume main tab) and the "Geo-Replication Sessions" main tab?</font></div> <div><font style="font-size: 13px;" face="Arial"><br> </font></div> <div><font style="font-size: 13px;" face="Arial">The only difference is that the one from the main tab would additionally ask the source (host / IP Address + volume).  For the detail tab, instead of prompting for the source, we can show it.</font></div> </blockquote> <br> <font face="Arial">Yes, it can be the same dialog. The information regarding source volume would be prefilled if it's coming from the geo-replication sub-tab.<br> <br> <br> </font> <blockquote cite="mid:EDB5A6A7-C6ED-4A4A-A15C-5405FF771F92@redhat.com" type="cite"> <div><font style="font-size: 13px;" face="Arial"><br> </font></div> <div><font style="font-size: 13px;" face="Arial">For the Destination (or Remote) Cluster Volumes, can the destination volume be of a different volume type to participate in geo-replication?</font></div> </blockquote> <br> <font face="Arial">Destination volume can be of a different volume type.</font><br> <br> <blockquote cite="mid:EDB5A6A7-C6ED-4A4A-A15C-5405FF771F92@redhat.com" type="cite"> <div><font style="font-size: 13px;" face="Arial"><br> </font></div> <div><font style="font-size: 13px;" face="Arial">For the Geo-Replication Session Options, can we make the configuration options (<a moz-do-not-send="true" href="https://access.redhat.com/documentation/en-US/Red_Hat_Storage/2.1/html/Admi…">https://access.redhat.com/documentation/en-US/Red_Hat_Storage/2.1/html/Admi…</a>) more usable vs. cryptic as it currently seems?  Specifically, can we showcase the defaults and provide the rest as Advanced configurations that they can change?</font></div> </blockquote> <br> We were planning to have a UI similar to the volume options. Do let us know, if there's a better way to do this.<br> <br> <blockquote cite="mid:EDB5A6A7-C6ED-4A4A-A15C-5405FF771F92@redhat.com" type="cite"> <div><font style="font-size: 13px;" face="Arial"><br> </font></div> <div><font style="font-size: 13px;" face="Arial">The Geo-Replication Session Details view -- I'm not sure what this is telling the user other then how long the host has been up.  Does this mean that replication has been running for as long as the uptime for those hosts?  It seems to be missing Checkpoint information and Checkpoint history information, which is important for geo-replication consistency.</font></div> <div><font style="font-size: 13px;" face="Arial"><br> </font></div> <div><font style="font-size: 13px;" face="Arial">Specifically, when I think of what is typically shown in a geo-replication session, I'd expect to see the following columns of information:</font></div> <div><font style="font-size: 13px;" face="Arial"><br> </font></div> <div><font style="font-size: 13px;" face="Arial">   Source Volume, Destination / Remote Volume, Status, Last Checkpoint, Last Checkpoint Label</font></div> <div><font style="font-size: 13px;" face="Arial"><br> </font></div> <div><font style="font-size: 13px;" face="Arial">If different volume types can be used within the same replication session, then we would also want to show the volume type on the remote volume.</font></div> </blockquote> <br> <font face="Arial">Session details view will also show information on files/bytes skipped, moved</font> etc per brick node.<br> <br> Regarding checkpoint, there's currently only a checkpoint status being shown. There's some enhancements to be done in gluster geo-rep with regards to checkpoints<br> <br> What information would need to be shown in checkpoint history?<br> <br> <br> <blockquote cite="mid:EDB5A6A7-C6ED-4A4A-A15C-5405FF771F92@redhat.com" type="cite"> <div><font style="font-size: 13px;" face="Arial"><br> </font></div> <div><font style="font-size: 13px;" face="Arial">BTW, do you know if there are plans to show volume size (total, used, available/remaining) in the Volume master area?</font></div> </blockquote> <br> <font face="Arial">Yes, we have introduced a volume capacity column in the Volumes tab, which will show these details.<br> <br> </font> <blockquote cite="mid:EDB5A6A7-C6ED-4A4A-A15C-5405FF771F92@redhat.com" type="cite"> <div><font style="font-size: 13px;" face="Arial"><br> </font></div> <div><font style="font-size: 13px;" face="Arial">Is there any possibility to change the terminology from master-slave to source-destination, source-remote, master-remote?  The master-slave terminology is quite unusual in the storage replication realm.  I ask as I see docs, CLI, etc. that already use the master-slave terminology.</font></div> </blockquote> <br> <font face="Arial">We could change in the docs and UI...CLI, not so sure.<br> <br> <br> </font> <blockquote cite="mid:EDB5A6A7-C6ED-4A4A-A15C-5405FF771F92@redhat.com" type="cite"> <div><font style="font-size: 13px;" face="Arial"><br> </font></div> <div><font style="font-size: 13px;" face="Arial">We're happy to put together mockups and/or a proposal if it would be helpful.  Is this the best way to provide input, or should I be posting my comments on <a moz-do-not-send="true" href="http://www.ovirt.org/Talk:Features/Gluster_Geo_Replication">http://www.ovirt.org/Talk:Features/Gluster_Geo_Replication</a>?</font></div> </blockquote> <br> <font face="Arial">If you have suggestions on showing the configuration options and for the dashboard, that would be welcome.<br> I could forward this to ovirt users for wider circulation.<br> <br> thanks!<br> <br> </font> <blockquote cite="mid:EDB5A6A7-C6ED-4A4A-A15C-5405FF771F92@redhat.com" type="cite"> <div><font style="font-size: 13px;" face="Arial"><br> </font></div> <div><font style="font-size: 13px;" face="Arial">Please advise.</font></div> <div><font style="font-size: 13px;" face="Arial"><br> </font></div> <div><font style="font-size: 13px;" face="Arial">Thanks,</font></div> <div><font style="font-size: 13px;" face="Arial">Ju</font></div> <div style="font-family: Noteworthy-Light; font-size: 15px; "><br> </div> <div><br> </div> <div> <div>On Sep 4, 2014, at 10:23 AM, Sahina Bose <<a moz-do-not-send="true" href="mailto:sabose@redhat.com">sabose(a)redhat.com</a>> wrote:</div> <br class="Apple-interchange-newline"> <blockquote type="cite">Hi all,<br> <br> The user experience section <a moz-do-not-send="true" href="http://www.ovirt.org/Features/Gluster_Geo_Replication#User_Experience">http://www.ovirt.org/Features/Gluster_Geo_Replication#User_Experience</a> , has been updated to capture the user flows. (The mockups, however, are older and do not completely reflect the updated text)<br> <br> There are couple of open questions. Please review and provide suggestions.<br> <br> thanks<br> sahina<br> <br> </blockquote> </div> <br> </blockquote> <br> </div> </blockquote> </div> <br> </div> <br> </div> <br> </body> </html> --------------070706000003030108020808--

1 0

Packages for 3.4.4 GA
by Sandro Bonazzola 23 Sep '14

23 Sep '14

1 0

[QE][ACTION REQUIRED] oVirt 3.5.0 status - Go / No Go
by Sandro Bonazzola 22 Sep '14

22 Sep '14

Hi, We are supposed to start composing oVirt 3.5.0 GA (or RC3, depending on this morning Go / No go Meeting decisions) I think we can use this email for discussing / voting 3.5.0 GA release. Looking at bugzilla status, I vote no go. I also think we should move the build to Wed allowing maintainers to fix pending blockers. Maintainers: - Please be sure that 3.5 snapshot satisfy release criteria[9] - Please be sure that no pending patches are going to block the release - If any patch must block the GA release please raise the issue as soon as possible. - If any packages need a rebase please raise the issue as soon as possible. - Be aware that packages that doesn't need a rebase must be re-built with final release versioning from the RC2 tag. The bug tracker [1] shows the following proposed blockers to be reviewed: Bug ID Whiteboard Status Summary 1143042 infra POST Repeated error "Failed to create VM external-test" when starting new VM 1143860 infra POST Marshaling issue in fencing policy using jsonrpc 1142256 integration NEW remote engine-reports-setup does not write conf file to allow accessing reports from engine 1144079 integration ASSIGNED local engine-reports-setup does not write conf file to allow accessing reports from engine The following bugs are keyworded as Regression and not marked as blockers[10] Bug ID Whiteboard Status Summary 1142709 integration NEW Trying to deploy hosted-engine via iSCSI device fails 1138144 storage NEW Failed to autorecover storage domain after unblocking connection with host 1118349 storage NEW [vdsm] Creating DataCenter 3.5 using master domain V1 fails with InquireNotSupportedError 1138314 virt NEW Fail to start vm with payload. Feature freeze is now effective, and branch has been created. All new patches must be backported to 3.5 branch too. Features completed are marked in green on Features Status Table [2] There are still 77 bugs [3] targeted to 3.5.0. Excluding node and documentation bugs we still have 53 bugs [4] targeted to 3.5.0. More in detail [5]: Whiteboard NEW ASSIGNED POST Total docs 13 1 0 14 gluster 8 2 2 12 i18n 0 0 1 1 infra 1 0 3 4 integration 1 2 1 4 node 7 4 0 11 ppc 2 0 4 6 sla 12 0 7 19 virt 3 0 3 6 Total 47 9 21 77 Maintainers / Assignee: - Please ensure that completed features are marked in green on Features Status Table [2] - If you find a blocker bug please remember to add it to the tracker [1] - Please fill release notes, the page has been created here [6] - Please review results from Third Test Day on the etherpad [7] and on the mailing lists - Please update the target to 3.5.1 or later for bugs that won't be in 3.5.0: it will ease gathering the blocking bugs for next releases. Community: - You're welcome to join us testing last release candidate or nightly builds and getting involved in oVirt Quality Assurance[8] [1] http://bugzilla.redhat.com/1073943 [2] http://goo.gl/4SuYdE [3] http://red.ht/1pVEk7H [4] http://red.ht/1zT2mSq [5] http://red.ht/1q7SqNL [6] http://www.ovirt.org/OVirt_3.5_Release_Notes [7] http://etherpad.ovirt.org/p/3.5-testday-3 [8] http://www.ovirt.org/OVirt_Quality_Assurance [9] http://www.ovirt.org/OVirt_3.5_release-management#Release_Criteria_.28WIP.29 [10] http://goo.gl/uavikG Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

4 4

Stable branch gerrit hook and Related-To: bug
by Martin Sivak 21 Sep '14

21 Sep '14

Hi, I would like to ask if it might be possible for the gerrit hook to stop giving -1 to patches that do not have bug-url, but have related-to. The reason for this is that I have a rather large patchset that is adding a new feature. No single patch by itself fixes the referenced bug and there are also patches that are not related to the feature itself, but were backported because they did some refactoring that was needed for the code to apply and/or work properly. -- Martin Sivák msivak(a)redhat.com Red Hat Czech RHEV-M SLA / Brno, CZ

9 19