<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 21, 2015 at 1:18 PM, Diem Tran <span dir="ltr"><<a href="mailto:diem.tran@oracle.com" target="_blank">diem.tran@oracle.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
  
    
  
  <div bgcolor="#FFFFFF" text="#000000">
    Hi Duncan,<br>
    <br>
    We totally understand that CI is not a box ticking exercise, it
    actually serves a purpose, and we are fully on board with the need
    for CI. We have resources monitoring the CI results and handling
    failures on daily basis.<br></div></blockquote><div><br></div><div>I still don't see any successful runs:</div><div><br></div><div><a href="http://paste.openstack.org/show/205029/">http://paste.openstack.org/show/205029/</a><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">
    <br>
    As far as the failures, we have resolved all issues related to our
    drivers that occur during the weekend (hence the failures). My
    understanding is that some time due to instability of devstack,
    there might be intermittent failures not related to out drivers at
    all, such as this:<br>
    <a href="https://review.openstack.org/#/c/168177/" target="_blank">https://review.openstack.org/#/c/168177/</a><br>
    <br>
    Thanks,<br>
    Diem.<div><div class="h5"><br>
    <br>
    <div>On 04/21/2015 03:40 PM, Duncan Thomas
      wrote:<br>
    </div>
    <blockquote type="cite">
      <p dir="ltr">Can you please investigate and comment here on this
        thread as to why your CI is failing for all patches? If this is
        not resolved, your driver will not be re-added, and ignoring
        requests to investigate CI failures will increase the chances of
        your driver being removed in future, without notice. Setting up
        a CI system is not a box ticking exercise, it requires
        monitoring and maintenance. If that is not possible then you are
        not yet in a position to be added back into cinder.</p>
      <div class="gmail_quote">On 21 Apr 2015 19:32, "Diem Tran" <<a href="mailto:diem.tran@oracle.com" target="_blank">diem.tran@oracle.com</a>>
        wrote:<br type="attribution">
        <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><br>
          On 04/21/2015 01:01 PM, Mike Perez wrote:<br>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
            On 09:57 Apr 21, Mike Perez wrote:<br>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
              On 15:47 Apr 20, Diem Tran wrote:<br>
              <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
                Hi Mike,<br>
                <br>
                Oracle ZFSSA iSCSI CI is now reporting test results. It
                is configured<br>
                to run against the ZFSSA iSCSI driver. You can see the
                results here:<br>
                <a href="https://review.openstack.org/#/q/reviewer:%22Oracle+ZFSSA+CI%22,n,z" target="_blank">https://review.openstack.org/#/q/reviewer:%22Oracle+ZFSSA+CI%22,n,z</a><br>
                <br>
                Below are some patchsets that the CI reports:<br>
                <a href="https://review.openstack.org/#/c/168424/" target="_blank">https://review.openstack.org/#/c/168424/</a><br>
                <a href="https://review.openstack.org/#/c/168419/" target="_blank">https://review.openstack.org/#/c/168419/</a><br>
                <a href="https://review.openstack.org/#/c/175247/" target="_blank">https://review.openstack.org/#/c/175247/</a><br>
                <a href="https://review.openstack.org/#/c/175077/" target="_blank">https://review.openstack.org/#/c/175077/</a><br>
                <a href="https://review.openstack.org/#/c/163706/" target="_blank">https://review.openstack.org/#/c/163706/</a><br>
                <br>
                <br>
                I would like to kindly request you and the core team to
                get the<br>
                Oracle ZFSSA iSCSI driver re-integrated back to the
                Cinder code base.<br>
                If there is anything else you need from the CI and the
                driver, please<br>
                do let me know.<br>
              </blockquote>
              This was done on 4/8:<br>
              <br>
              <a href="https://review.openstack.org/#/c/170770/" target="_blank">https://review.openstack.org/#/c/170770/</a><br>
            </blockquote>
            My mistake this was only the NFS driver. The window to have
            drivers readded in<br>
            Kilo has long past. Please see:<br>
            <br>
            <a href="http://lists.openstack.org/pipermail/openstack-dev/2015-March/059990.html" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/2015-March/059990.html</a><br>
            <br>
            This will have to be readded in Liberty only at this point.<br>
          </blockquote>
          <br>
          Thank you for your reply. Could you please let me know the
          procedure needed for the driver to be readded to Liberty?
          Specifically, will you be the one who upload the revert
          patchset, or it is the driver maintainer's responsibility?<br>
          <br>
          Diem.<br>
          <br>
          <br>
          <br>
__________________________________________________________________________<br>
          OpenStack Development Mailing List (not for usage questions)<br>
          Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
          <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
        </blockquote>
      </div>
      <br>
      <fieldset></fieldset>
      <br>
      <pre>__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
    </blockquote>
    <br>
  </div></div></div>

<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>