<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 17, 2018 at 10:52 AM, Sofer Athlan-Guyot <span dir="ltr"><<a href="mailto:sathlang@redhat.com" target="_blank">sathlang@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">Emilien Macchi <<a href="mailto:emilien@redhat.com">emilien@redhat.com</a>> writes:<br>
<br>
> Nice work Sofer!<br>
> I have a few questions, see inline.<br>
><br>
> On Wed, Jan 17, 2018 at 4:46 AM, Sofer Athlan-Guyot <<a href="mailto:sathlang@redhat.com">sathlang@redhat.com</a>> wrote:<br>
>> Hi,<br>
>><br>
>> So join us (upgrade squad) to celebrate the working ocata->pike upgrade<br>
>> job[1], without any depends-on whatsoever.<br>
><br>
> w00t, really good work!<br>
><br>
>> We would like it to be voting as soon as possible. It has been a<br>
>> rather consuming task to revive that forgotten but important jobs, and<br>
>> the only way for it to not drift into oblivion again is to have it<br>
>> voting.<br>
><br>
> The last time I asked how we could make RDO jobs voting, it was<br>
> something in Software Factory to enable, but I'm not sure about the<br>
> details.<br>
> I'm ok to make them voting, as long as:<br>
><br>
> - they don't timeout or reach the timeout limit (which isn't the case<br>
> now, 2h27 is really good)<br>
> - they proved to be stable during some time<br>
> - they're part of the promotion pipeline so gate can't break easily<br>
><br>
> BTW the process is documented here:<br>
> <a href="https://github.com/openstack/tripleo-specs/blob/master/specs/policy/adding-ci-jobs.rst" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>tripleo-specs/blob/master/<wbr>specs/policy/adding-ci-jobs.<wbr>rst</a><br>
<br>
</span>Oki reading that, thanks for the pointer.<br>
<span class="gmail-"><br>
>> Eventually, let’s thanks rdo-cloud people for their support (especially<br>
>> David Manchado), James Slagle for Traas[2] and Alfredo Moralejo for his<br>
>> constant availability to answer our questions.<br>
><br>
> ++<br>
><br>
>><br>
>> Thanks,<br>
>><br>
>> [1] <a href="https://review.openstack.org/#/c/532791/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/532791/</a>, look for «gate-tripleo-ci-centos-7-<wbr>containers-multinode-upgrades-<wbr>pike»<br>
>> [2] <a href="https://github.com/slagle/traas" rel="noreferrer" target="_blank">https://github.com/slagle/<wbr>traas</a> … the repo we use -> <a href="https://github.com/sathlan/traas" rel="noreferrer" target="_blank">https://github.com/sathlan/<wbr>traas</a> (so many pull requests to make that it would be cool for it to be an openstack project … :))<br>
><br>
> Please rebase <a href="https://github.com/slagle/traas/pull/9" rel="noreferrer" target="_blank">https://github.com/slagle/<wbr>traas/pull/9</a> and address<br>
> James's comments, so we can avoid using a fork.<br>
<br>
</span>So yeah, the situation with traas is not so good as we have a 70 patches<br>
difference with the main repo.  The pull/9 may be abandoned (jfrancoa<br>
will see if it’s still required) in favor of the what’s in<br>
<a href="https://github.com/sathlan/traas" rel="noreferrer" target="_blank">https://github.com/sathlan/<wbr>traas</a> .  We’re going to work toward pulling<br>
in slage/traas the main patches to avoid a fork.<br></blockquote><div><br></div><div>Sofer, it's probably worth everyone's time to consider reviewing and testing</div><div>the script provided in the logs with the successful upgrade itself to debug and recreate upgrade jobs.</div><div><br></div><div><a href="https://logs.rdoproject.org/91/532791/6/openstack-check/gate-tripleo-ci-centos-7-containers-multinode-upgrades-pike/Z0ac437d8cf634d4a8e1eca18b6dd0061/reproducer-quickstart.sh">https://logs.rdoproject.org/91/532791/6/openstack-check/gate-tripleo-ci-centos-7-containers-multinode-upgrades-pike/Z0ac437d8cf634d4a8e1eca18b6dd0061/reproducer-quickstart.sh</a><br></div><div><br></div><div>Thanks</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<span class="gmail-"><br>
> Also, any plan to run tempest instead of pingtest?<br>
<br>
</span>Not yet.  We could cycle back to that at a later point in time, unless<br>
it’s a requirement.  Currently I’ve added it to our backlog.<br>
<br>
A last point is that we may add ceph in the mix based on what it’s done<br>
in scenario 001 and 004.<br>
<span class="gmail-im gmail-HOEnZb"><br>
><br>
> Thanks,<br>
> --<br>
> Emilien Macchi<br>
><br>
> ______________________________<wbr>______________________________<wbr>______________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
</span><span class="gmail-HOEnZb"><font color="#888888">--<br>
Chem<br>
</font></span><div class="gmail-HOEnZb"><div class="gmail-h5"><br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
</div></div></blockquote></div><br></div></div>