<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Hi.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">We’ve completed integrating manager.py into openstack/ironic.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><a href="https://review.openstack.org/#/c/439252/">https://review.openstack.org/#/c/439252/</a> (include local copy)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><a href="https://review.openstack.org/#/c/446844/">https://review.openstack.org/#/c/446844/</a> (prune local copy)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">-Solio<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:Calibri;color:black">From: </span>
</b><span style="font-family:Calibri;color:black">Andrea Frittoli <andrea.frittoli@gmail.com><br>
<b>Reply-To: </b>"OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org><br>
<b>Date: </b>Tuesday, March 7, 2017 at 3:28 PM<br>
<b>To: </b>"OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org><br>
<b>Subject: </b>Re: [openstack-dev] [QA][blazar][ceilometer][congress][intel-nfv-ci-tests][ironic][manila][networking-bgpvpn][networking-fortinet][networking-sfc][neutron][neutron-fwaas][neutron-lbaas][nova-lxd][octavia][sahara][tap-as-a-service][horizon][vmware-nsx][...<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Hi, <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">an update on this.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">It's about 10days since the original message, and the current status is:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">- 3 patches merged, 1 approved (recheck)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">- 5 patches submitted, pending approval<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">- 2 patches with a -1 (need more work)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">- 7 patches submitted by me today (draft) - review needed<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thank you for your work on this!<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I would recommend to prune the imported module as much as possible as well.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">It would make it easier for the QA team to identify which interfaces on Tempest side should be migrated to stable.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">andrea<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Wed, Mar 1, 2017 at 1:25 PM Andrea Frittoli <<a href="mailto:andrea.frittoli@gmail.com">andrea.frittoli@gmail.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<div>
<p class="MsoNormal">On Wed, Mar 1, 2017 at 2:21 AM Takashi Yamamoto <<a href="mailto:yamamoto@midokura.com" target="_blank">yamamoto@midokura.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal" style="margin-bottom:12.0pt">hi,<br>
<br>
On Mon, Feb 27, 2017 at 8:34 PM, Andrea Frittoli<br>
<<a href="mailto:andrea.frittoli@gmail.com" target="_blank">andrea.frittoli@gmail.com</a>> wrote:<br>
> Hello folks,<br>
><br>
> TL;DR: if today you import manager,py from tempest.scenario please maintain<br>
> a copy of [0] in tree until further notice.<br>
><br>
> Full message:<br>
> ------------------<br>
><br>
> One of the priorities for the QA team in the Pike cycle is to refactor<br>
> scenario tests to a sane code base [1].<br>
><br>
> As they are now, changes to scenario tests are difficult to develop and<br>
> review, and failures in those tests are hard to debug, which is in many<br>
> directions far away from where we need to be.<br>
><br>
> The issue we face is that, even though tempest.scenario.manager is not<br>
> advertised as a stable interface in Tempest, many project use it today for<br>
> convenience in writing their own tests. We don't know about dependencies<br>
> outside of the OpenStack ecosystem, but we want to try to make this refactor<br>
> a smooth experience for our uses in OpenStack, and avoid painful gate<br>
> breakages as much as possible.<br>
><br>
> The process we're proposing is as follows:<br>
> - hold a copy of [0] in tree - in most cases you won't even have to change<br>
> your imports as a lot of projects use tempest/scenario in their code base.<br>
> You may decide to include the bare minimum you need from that module instead<br>
> of all of it. It's a bit more work to make the patch, but less un-used code<br>
> lying around afterwards.<br>
<br>
i submitted patches for a few repos.<br>
<a href="https://review.openstack.org/#/q/status:open++branch:master+topic:tempest-manager" target="_blank">https://review.openstack.org/#/q/status:open++branch:master+topic:tempest-manager</a><br>
i'd suggest to use the same gerrit topic for relevant patches.<o:p></o:p></p>
</blockquote>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal">Thank you for looking into this!<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Having a common gerrit topic is a nice idea: "tempest-manager"<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I'm also tracking patches in this etherpad: <a href="https://etherpad.openstack.org/p/tempest-manager-plugins" target="_blank">https://etherpad.openstack.org/p/tempest-manager-plugins</a> <o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">andrea <o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">> - the QA team will refactor scenario tests, and make more interfaces stable<br>
> (test.py, credential providers). We won't advertise every single change in<br>
> this process, only when we start and once we're done.<br>
> - you may decide to discard your local copy of manager.py and consume<br>
> Tempest stable interfaces directly. We will help with any question you may<br>
> have on the process and on Tempest interfaces.<br>
><br>
> Repositories affected by the refactor are (based on [2]):<br>
><br>
> blazar,ceilometer,congress,intel-nfv-ci-tests,ironic,manila,networking-bgpvpn,networking-fortinet,networking-sfc,neutron-fwaas,neutron-lbaas,nova-lxd,octavia,sahara-tests,tap-as-a-service,tempest-horizon,vmware-nsx,watcher<br>
><br>
> If we don't hear from a team at all in the next two weeks, we will assume<br>
> that the corresponding Tempest plugin / bunch of tests is not in use<br>
> anymore, and ignore it. If you use <a href="http://tempest.scenario.manager.py" target="_blank">
tempest.scenario.manager.py</a> today and<br>
> your repo is not on the list, please let us know!<br>
><br>
> I'm happy to propose an initial patch for any team that may require it -<br>
> just ping me on IRC (andreaf).<br>
> I won't have the bandwidth myself to babysit each patch through review and<br>
> gate though.<br>
><br>
> Thank you for your cooperation and patience!<br>
><br>
> Andrea<br>
><br>
> [0]<br>
> <a href="http://git.openstack.org/cgit/openstack/tempest/tree/tempest/scenario/manager.py" target="_blank">
http://git.openstack.org/cgit/openstack/tempest/tree/tempest/scenario/manager.py</a><br>
> [1] <a href="https://etherpad.openstack.org/p/pike-qa-priorities" target="_blank">
https://etherpad.openstack.org/p/pike-qa-priorities</a><br>
> [2]<br>
> <a href="https://github.com/andreafrittoli/tempest_stable_interfaces/blob/master/data/get_deps.sh" target="_blank">
https://github.com/andreafrittoli/tempest_stable_interfaces/blob/master/data/get_deps.sh</a><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>
><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><o:p></o:p></p>
</blockquote>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</body>
</html>