<html xmlns:v="urn:schemas-microsoft-com:vml" 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="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@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;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
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;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:597298380;
mso-list-template-ids:723804160;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">That’s should works for now.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I will get my team to upload the heat template to
<a href="https://github.com/openstack/osops-tools-contrib/%3cheat%3e">https://github.com/openstack/osops-tools-contrib/<heat></a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">On the 2<sup>nd</sup> point, Heat itself doesn’t upload test results.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Are we also responsible for creating the “Test Result Upload Script”?
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></a></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><a name="_____replyseparator"></a><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Tong Li [mailto:litong01@us.ibm.com]
<br>
<b>Sent:</b> Thursday, August 4, 2016 5:10 AM<br>
<b>To:</b> Sun, Yih Leong <yih.leong.sun@intel.com><br>
<b>Cc:</b> akapadia@mirantis.com; Randal, Allison <allison.randal@hpe.com>; Anni.Lai@huawei.com; Brad Topol <btopol@us.ibm.com>; brenski@mirantis.com; Barrett, Carol L <carol.l.barrett@intel.com>; Catherine Cuong Diep <cdiep@us.ibm.com>; Brown, David L <david.l.brown@intel.com>;
defcore-committee <defcore-committee@lists.openstack.org>; dn283x@att.com; ee550x@att.com; egle.sigler@rackspace.com; Evans, Eileen <eileen.evans@hpe.com>; Elizabeth Kueper <ekueper@us.ibm.com>; Stewart, Gretchen <gretchen.stewart@intel.com>; Janssen, Hank
H. <hank.janssen@hpe.com>; huangzhipeng@huawei.com; Jason Kennedy <jkomg@us.ibm.com>; Meyer, Jim <jim.meyer@hpe.com>; Johanna Koester <koester@us.ibm.com>; Woodburn, John L <john.l.woodburn@intel.com>; McRoberts, Julie <julie.mcroberts@intel.com>; kaneshige.kenji@jp.fujitsu.com;
letucker@cisco.com; liyongle@huawei.com; Cazares, Luz <luz.cazares@intel.com>; manju.ramanathpura@hds.com; Bonell Manjarrez, Marcela <marcela.bonell.manjarrez@intel.com>; markmc@redhat.com; mark.baker@canonical.com; Apostol, Michael J <michael.j.apostol@intel.com>;
mvoelker@vmware.com; nijaba@redhat.com; Strottman, Nissa <nissa.strottman@hpe.com>; pchadwick@suse.com; Yeluri, Raghuram <raghuram.yeluri@intel.com>; rbryant@redhat.com; roagarwa@cisco.com; Rob.Esker@netapp.com; Rochelle Grober <rochelle.grober@huawei.com>;
Sodoma, Scott <scott.sodoma@intel.com>; Shamail Tahir <stahir@us.ibm.com>; soniarvind@vmware.com; TF4242@att.com; Travis Mcpeak <tmcpeak@us.ibm.com>; Vince Brunssen <brunssen@us.ibm.com><br>
<b>Subject:</b> Re: [interop-challenge] osops repo for heat Template<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p>Leong,<br>
I have the same question. Since some of the projects are already in contrib repo, I suggest we continue using that unless someone create a brand new bearing openstack path of course. Here is what I suggest:<br>
<br>
1. Still use this repo <a href="https://github.com/openstack/osops-tools-contrib">
https://github.com/openstack/osops-tools-contrib</a> for work load scripts, create heat sub directory at the location where terraform currently is. create other sub directories when other tools are adopted.<br>
2. Find a restful api capable storage to save test results so that these work load scripts will automatically upload the test results to the location after each run (runner can indicate if the results should be uploaded or not with a flag)<br>
<br>
Thanks.<br>
<br>
Tong Li<br>
IBM Open Technology<br>
Building 501/B205<br>
<a href="mailto:litong01@us.ibm.com">litong01@us.ibm.com</a><br>
<br>
<img border="0" width="16" height="16" id="_x0000_i1025" src="cid:image001.gif@01D1EE32.E0DF6F90" alt="Inactive hide details for "Sun, Yih Leong" ---08/03/2016 02:04:09 PM---Hi all, In today interop-challenge meeting, the team dec"><span style="color:#424282">"Sun,
Yih Leong" ---08/03/2016 02:04:09 PM---Hi all, In today interop-challenge meeting, the team decided to use the osops-tools-contrib repo [1]</span><br>
<br>
<span style="font-size:10.0pt;color:#5F5F5F">From: </span><span style="font-size:10.0pt">"Sun, Yih Leong" <<a href="mailto:yih.leong.sun@intel.com">yih.leong.sun@intel.com</a>></span><br>
<span style="font-size:10.0pt;color:#5F5F5F">To: </span><span style="font-size:10.0pt">Johanna Koester/Raleigh/IBM@IBMUS, "Meyer, Jim" <<a href="mailto:jim.meyer@hpe.com">jim.meyer@hpe.com</a>></span><br>
<span style="font-size:10.0pt;color:#5F5F5F">Cc: </span><span style="font-size:10.0pt">"<a href="mailto:akapadia@mirantis.com">akapadia@mirantis.com</a>" <<a href="mailto:akapadia@mirantis.com">akapadia@mirantis.com</a>>, "Randal, Allison" <<a href="mailto:allison.randal@hpe.com">allison.randal@hpe.com</a>>,
"<a href="mailto:Anni.Lai@huawei.com">Anni.Lai@huawei.com</a>" <<a href="mailto:Anni.Lai@huawei.com">Anni.Lai@huawei.com</a>>, Brad Topol/Raleigh/IBM@IBMUS, "<a href="mailto:brenski@mirantis.com">brenski@mirantis.com</a>" <<a href="mailto:brenski@mirantis.com">brenski@mirantis.com</a>>,
"Barrett, Carol L" <<a href="mailto:carol.l.barrett@intel.com">carol.l.barrett@intel.com</a>>, Catherine Cuong Diep/San Jose/IBM@IBMUS, "Brown, David L" <<a href="mailto:david.l.brown@intel.com">david.l.brown@intel.com</a>>, "<a href="mailto:dn283x@att.com">dn283x@att.com</a>"
<<a href="mailto:dn283x@att.com">dn283x@att.com</a>>, "<a href="mailto:ee550x@att.com">ee550x@att.com</a>" <<a href="mailto:ee550x@att.com">ee550x@att.com</a>>, "<a href="mailto:egle.sigler@rackspace.com">egle.sigler@rackspace.com</a>" <<a href="mailto:egle.sigler@rackspace.com">egle.sigler@rackspace.com</a>>,
"Evans, Eileen" <<a href="mailto:eileen.evans@hpe.com">eileen.evans@hpe.com</a>>, Elizabeth Kueper/Rochester/IBM@IBMUS, "Stewart, Gretchen" <<a href="mailto:gretchen.stewart@intel.com">gretchen.stewart@intel.com</a>>, "Janssen, Hank H." <<a href="mailto:hank.janssen@hpe.com">hank.janssen@hpe.com</a>>,
"<a href="mailto:huangzhipeng@huawei.com">huangzhipeng@huawei.com</a>" <<a href="mailto:huangzhipeng@huawei.com">huangzhipeng@huawei.com</a>>, Jason Kennedy/Seattle/IBM@IBMUS, "Woodburn, John L" <<a href="mailto:john.l.woodburn@intel.com">john.l.woodburn@intel.com</a>>,
"McRoberts, Julie" <<a href="mailto:julie.mcroberts@intel.com">julie.mcroberts@intel.com</a>>, "<a href="mailto:kaneshige.kenji@jp.fujitsu.com">kaneshige.kenji@jp.fujitsu.com</a>" <<a href="mailto:kaneshige.kenji@jp.fujitsu.com">kaneshige.kenji@jp.fujitsu.com</a>>,
"<a href="mailto:letucker@cisco.com">letucker@cisco.com</a>" <<a href="mailto:letucker@cisco.com">letucker@cisco.com</a>>, "<a href="mailto:liyongle@huawei.com">liyongle@huawei.com</a>" <<a href="mailto:liyongle@huawei.com">liyongle@huawei.com</a>>, "Cazares,
Luz" <<a href="mailto:luz.cazares@intel.com">luz.cazares@intel.com</a>>, "<a href="mailto:manju.ramanathpura@hds.com">manju.ramanathpura@hds.com</a>" <<a href="mailto:manju.ramanathpura@hds.com">manju.ramanathpura@hds.com</a>>, "Bonell Manjarrez, Marcela"
<<a href="mailto:marcela.bonell.manjarrez@intel.com">marcela.bonell.manjarrez@intel.com</a>>, "<a href="mailto:markmc@redhat.com">markmc@redhat.com</a>" <<a href="mailto:markmc@redhat.com">markmc@redhat.com</a>>, "<a href="mailto:mark.baker@canonical.com">mark.baker@canonical.com</a>"
<<a href="mailto:mark.baker@canonical.com">mark.baker@canonical.com</a>>, "Apostol, Michael J" <<a href="mailto:michael.j.apostol@intel.com">michael.j.apostol@intel.com</a>>, "<a href="mailto:mvoelker@vmware.com">mvoelker@vmware.com</a>" <<a href="mailto:mvoelker@vmware.com">mvoelker@vmware.com</a>>,
"<a href="mailto:nijaba@redhat.com">nijaba@redhat.com</a>" <<a href="mailto:nijaba@redhat.com">nijaba@redhat.com</a>>, "Strottman, Nissa" <<a href="mailto:nissa.strottman@hpe.com">nissa.strottman@hpe.com</a>>, "<a href="mailto:pchadwick@suse.com">pchadwick@suse.com</a>"
<<a href="mailto:pchadwick@suse.com">pchadwick@suse.com</a>>, "Yeluri, Raghuram" <<a href="mailto:raghuram.yeluri@intel.com">raghuram.yeluri@intel.com</a>>, "<a href="mailto:rbryant@redhat.com">rbryant@redhat.com</a>" <<a href="mailto:rbryant@redhat.com">rbryant@redhat.com</a>>,
"<a href="mailto:roagarwa@cisco.com">roagarwa@cisco.com</a>" <<a href="mailto:roagarwa@cisco.com">roagarwa@cisco.com</a>>, "<a href="mailto:Rob.Esker@netapp.com">Rob.Esker@netapp.com</a>" <<a href="mailto:Rob.Esker@netapp.com">Rob.Esker@netapp.com</a>>, Rochelle
Grober <<a href="mailto:rochelle.grober@huawei.com">rochelle.grober@huawei.com</a>>, "Sodoma, Scott" <<a href="mailto:scott.sodoma@intel.com">scott.sodoma@intel.com</a>>, Shamail Tahir/Boston/IBM@IBMUS, "<a href="mailto:soniarvind@vmware.com">soniarvind@vmware.com</a>"
<<a href="mailto:soniarvind@vmware.com">soniarvind@vmware.com</a>>, "<a href="mailto:TF4242@att.com">TF4242@att.com</a>" <<a href="mailto:TF4242@att.com">TF4242@att.com</a>>, Tong Li/Raleigh/IBM@IBMUS, Travis Mcpeak/Silicon Valley/IBM@IBMUS, Vince Brunssen/Austin/IBM@IBMUS,
defcore-committee <<a href="mailto:defcore-committee@lists.openstack.org">defcore-committee@lists.openstack.org</a>></span><br>
<span style="font-size:10.0pt;color:#5F5F5F">Date: </span><span style="font-size:10.0pt">08/03/2016 02:04 PM</span><br>
<span style="font-size:10.0pt;color:#5F5F5F">Subject: </span><span style="font-size:10.0pt">[interop-challenge] osops repo for heat Template</span><o:p></o:p></p>
<div class="MsoNormal">
<hr size="2" width="100%" noshade="" style="color:#8091A5" align="left">
</div>
<p class="MsoNormal"><br>
<br>
<br>
Hi all,<br>
<br>
In today interop-challenge meeting, the team decided to use the osops-tools-contrib repo [1] for the template.<br>
There is a terraform folder, however, there is no “heat” folder at the directory structure. Should we create one for “heat”?<br>
<br>
How are we going to organize the directory structure in this repo for: <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in">1. Templates for testing purpose (heat, terraform, etc)<br>
2. Test results <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
Also, the README indicated that this osops-tools-contrib [1] place is untested and unverified.
<br>
Is there a plan for those “tested” template to move into osops-tools-generic [2]?<br>
<br>
[1] <a href="https://github.com/openstack/osops-tools-contrib">https://github.com/openstack/osops-tools-contrib</a><br>
[2] <a href="https://github.com/openstack/osops-tools-generic">https://github.com/openstack/osops-tools-generic</a><br>
<br>
Thanks!<br>
<br>
---<br>
Yih <b><u>Leong</u></b> Sun, PhD <br>
Senior Software Cloud Architect | Open Source Technology Center | Intel Corporation<br>
<a href="mailto:yih.leong.sun@intel.com"><span style="color:#0563C1">yih.leong.sun@intel.com</span></a> | +1 503 264 0610<br>
<br>
<br>
<br>
<o:p></o:p></p>
</div>
</body>
</html>