<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=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@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:11.0pt;
font-family:"Calibri","sans-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.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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 style="margin-bottom:12.0pt">> ><br>
> > What's the best way to make this list better?<br>
> <br>
> I would suggest to give us your take on the right way to consider <br>
> Swift capabilities give some of the background I’ve supplied. The only <br>
> additional caveat is that we need to be able to connect existing <br>
> Tempest tests to capabilities. We can then work on redoing that section of the scoresheet.<br>
> <br>
<br>
<o:p></o:p></p>
<p style="margin-bottom:12.0pt">We have not formalized this in DefCore or with the TC yet. My thought was that the PTLs for the projects would define/recommend the capability groups and map them to the tests. We need to move the capabilities mapping out of
a spreadsheet and into a controlled json file.<o:p></o:p></p>
<p style="margin-bottom:12.0pt">We’ve started that <a href="https://review.openstack.org/#/c/91640/">
https://review.openstack.org/#/c/91640/</a> <o:p></o:p></p>
</div>
</body>
</html>