<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 12 (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:"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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 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";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</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="Section1">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:#1F497D">Hi, folks.</span></b><span style="font-size:10.0pt;font-family:
"Tahoma","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:#1F497D">This is the email I sent to the interop@openstack.orb and the co-chairs of DefCore. From today's DefCore meeting, I am posting this to the mailing list for
discussion and hopefully resolution. Mark Voelker said that other vendors had also had the same issue. TL;DR a set of Nova tests changed between the time 2015.05 build SHA was captured and the 2015.07 SHA was captured. The changed tests were intended for
the LIberty release, as they were not proposed/merged until after the Kilo release Kilo release was April; changes to tests were merged June 19 (definitely in the Liberty cycle).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:#1F497D">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:#1F497D">--Rocky<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:#1F497D">Below, is more info on Huawei's situation:<o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:#1F497D"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal">Huawei has a problem we hope you can help us with. Our FusionSphere 6.0, based on Juno, qualified for the "interop" OpenStack Powered (tm) program on the 2015.05 DefCore tests. We are now trying to qualify our Public cloud offering,
running the exact same FusionSphere/OpenStack software but cannot pass a subset of the Nova tests.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Huawei uses Nova api V2 (not V2.1). As such, our implementation has "Additional Properties" enabled and used. These are supposedly valid operations for the Juno release.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The tests in question were changed via https://review.openstack.org/#/c/156130. AdditionalProperties were changed to "False" in all of the tests included in the review.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The problem is that Juno was released in October of 2014, with AdditionalProperties (extenstions) allowed in the v2 apis. The tests were changed for the Kilo release cycle, but affect the Juno releases under the Interop/DefCore/Refstack
test selection process because of the nonbranching nature of Tempest. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We think a waiver is appropriate in this situation, as the Huawei code has not changed, yet it now fails API tests that were valid three months earlier. We think that including the v2 api in the changes in theseDefCore tests was a mistake,
as the discussion below indicates, and that more care needs to be exercised when test changes are made to enforce new behaviors for later release cycles. We would be happy to demonstrate that our release still passes the failed tests under the older version
of those tests that exist in 2015.0<span style="color:#1F497D">5</span>. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We have been working diligently to get the certification on our Public Cloud product, and had hoped to qualify/certify before the release of the 2016.01 standards, as our development resources are currently focused on moving our product
to a more current OpenStack release.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Please advise us as to how we proceed from here.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Respectfully,<o:p></o:p></p>
<p class="MsoNormal">Rocky Grober and our FusionSphere team<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">an excerpt from one of the changed files:<o:p></o:p></p>
<p class="MsoNormal"><img width="1325" height="420" id="Picture_x0020_1" src="cid:image001.gif@01D14720.1F427670" alt="cid:image002.gif@01D13983.9475C460"><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt">The problem of a backward incompatibility to an API being introduced by test changes was mentioned in one an exchange in comments:<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in;background:white"><span style="font-family:"Arial","sans-serif";color:black">afazekas<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in;background:white"><span style="font-family:"Arial","sans-serif";color:black">Mar 17, 2015<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in;background:white"><span style="font-family:"Cambria Math","serif";color:black">↩</span><span style="font-family:"Arial","sans-serif";color:black"><o:p></o:p></span></p>
<p style="margin-left:.5in;background:white;-webkit-margin-before: 0px;
-webkit-margin-after: 0.3em;white-space:pre-wrap">
<span style="font-family:
"Arial","sans-serif";color:black">Patch Set 31: Code-Review-1<o:p></o:p></span></p>
<p style="margin-left:.5in;background:white;-webkit-margin-before: 0px;
-webkit-margin-after: 0.3em;white-space:pre-wrap">
<span style="font-family:
"Arial","sans-serif";color:black">Does not makes sense to prevent additional properties in tempest on something which allows extensions.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in;background:white"><span style="font-family:"Arial","sans-serif";color:black">Ghanshyam Mann<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in;background:white"><span style="font-family:"Arial","sans-serif";color:black">Mar 18, 2015<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in;background:white"><span style="font-family:"Cambria Math","serif";color:black">↩</span><span style="font-family:"Arial","sans-serif";color:black"><o:p></o:p></span></p>
<p style="margin-left:.5in;background:white;-webkit-margin-before: 0px;
-webkit-margin-after: 0.3em;white-space:pre-wrap">
<span style="font-family:
"Arial","sans-serif";color:black">Patch Set 31:<o:p></o:p></span></p>
<p style="margin-left:.5in;background:white;-webkit-margin-before: 0px;
-webkit-margin-after: 0.3em;white-space:pre-wrap">
<span style="font-family:
"Arial","sans-serif";color:black">@afazekas - Thanks for review.<o:p></o:p></span></p>
<p style="margin-left:.5in;background:white;-webkit-margin-before: 0px;
-webkit-margin-after: 0.3em;white-space:pre-wrap">
<span style="font-family:
"Arial","sans-serif";color:black">Actually all schema has been modified to work for all extension (as current tests runs for all extension enable).<o:p></o:p></span></p>
<p style="margin-left:.5in;background:white;-webkit-margin-before: 0px;
-webkit-margin-after: 0.3em;white-space:pre-wrap">
<span style="font-family:
"Arial","sans-serif";color:black">As v2 (v2.1) API are frozen, tempest should have additionalProperties False to capture any unwanted changes in those API.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in;background:white"><span style="font-family:"Arial","sans-serif";color:black">afazekas<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in;background:white"><span style="font-family:"Arial","sans-serif";color:black">Mar 18, 2015<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in;background:white"><span style="font-family:"Cambria Math","serif";color:black">↩</span><span style="font-family:"Arial","sans-serif";color:black"><o:p></o:p></span></p>
<p style="margin-left:.5in;background:white;-webkit-margin-before: 0px;
-webkit-margin-after: 0.3em;white-space:pre-wrap">
<span style="font-family:
"Arial","sans-serif";color:black">Patch Set 31:<o:p></o:p></span></p>
<p style="margin-left:.5in;background:white;-webkit-margin-before: 0px;
-webkit-margin-after: 0.3em;white-space:pre-wrap">
<span style="font-family:
"Arial","sans-serif";color:black"><a href="https://wiki.openstack.org/wiki/APIChangeGuidelines" target="_blank"><span style="color:#0654AC;text-decoration:none">https://wiki.openstack.org/wiki/APIChangeGuidelines</span></a><o:p></o:p></span></p>
<p style="margin-left:.5in;background:white;-webkit-margin-before: 0px;
-webkit-margin-after: 0.3em;white-space:pre-wrap">
<span style="font-family:
"Arial","sans-serif";color:black">"Adding a property to a resource representation" is generally acceptable.<o:p></o:p></span></p>
<p style="margin-left:.5in;background:white;-webkit-margin-before: 0px;
-webkit-margin-after: 0.3em;white-space:pre-wrap">
<span style="font-family:
"Arial","sans-serif";color:black">"Changing or removing a property in a resource representation" OR "Changing the semantics of a property in a resource representation which may be supplied by clients" is generally not acceptable.<o:p></o:p></span></p>
<p style="margin-left:.5in;background:white;-webkit-margin-before: 0px;
-webkit-margin-after: 0.3em;white-space:pre-wrap">
<span style="font-family:
"Arial","sans-serif";color:black">We do not need to prevent additional properties.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in;background:white"><span style="font-family:"Arial","sans-serif";color:black">Ghanshyam Mann<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in;background:white"><span style="font-family:"Arial","sans-serif";color:black">Mar 19, 2015<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in;background:white"><span style="font-family:"Cambria Math","serif";color:black">↩</span><span style="font-family:"Arial","sans-serif";color:black"><o:p></o:p></span></p>
<p style="margin-left:.5in;background:white;-webkit-margin-before: 0px;
-webkit-margin-after: 0.3em;white-space:pre-wrap">
<span style="font-family:
"Arial","sans-serif";color:black">Patch Set 31:<o:p></o:p></span></p>
<p style="margin-left:.5in;background:white;-webkit-margin-before: 0px;
-webkit-margin-after: 0.3em;white-space:pre-wrap">
<span style="font-family:
"Arial","sans-serif";color:black">Yea, those are acceptable and it used to done by adding new extension etc. But as v2 nd v2.1 are frozen and no new extension for thosse. All new attributes etc can be added with microversion only.
As it is done for first microversion - <a href="https://review.openstack.org/#/c/140313/" target="_blank">
<span style="color:#0654AC;text-decoration:none">https://review.openstack.org/#/c/140313/</span></a><o:p></o:p></span></p>
<p style="margin-left:.5in;background:white;-webkit-margin-before: 0px;
-webkit-margin-after: 0.3em;white-space:pre-wrap">
<span style="font-family:
"Arial","sans-serif";color:black">Please do let me know if m missing anything on this.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in;background:white"><span style="font-family:"Arial","sans-serif";color:black">Ken'ichi Ohmichi<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in;background:white"><span style="font-family:"Arial","sans-serif";color:black">Mar 19, 2015<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in;background:white"><span style="font-family:"Cambria Math","serif";color:black">↩</span><span style="font-family:"Arial","sans-serif";color:black"><o:p></o:p></span></p>
<p style="margin-left:.5in;background:white;-webkit-margin-before: 0px;
-webkit-margin-after: 0.3em;white-space:pre-wrap">
<span style="font-family:
"Arial","sans-serif";color:black">Patch Set 31: Code-Review+2<o:p></o:p></span></p>
<p style="margin-left:.5in;background:white;-webkit-margin-before: 0px;
-webkit-margin-after: 0.3em;white-space:pre-wrap">
<span style="font-family:
"Arial","sans-serif";color:black">Yeah, Ghanshyam is right.<o:p></o:p></span></p>
<p style="margin-left:.5in;background:white;-webkit-margin-before: 0px;
-webkit-margin-after: 0.3em;white-space:pre-wrap">
<span style="font-family:
"Arial","sans-serif";color:black">As <a href="http://lists.openstack.org/pipermail/openstack-dev/2015-February/057613.html" target="_blank">
<span style="color:#0654AC">http://lists.openstack.org/pipermail/openstack-dev/2015-February/057613.html</span></a> , new attributes will be added with microversions and v2(v2.1) should be frozen. So this change is necessary for blocking additional attributes
on v2 and v2.1 API.<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>