<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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
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 class="MsoNormal">Thanks to everyone who commented on the spec to change reset-state to involve the driver:
<a href="https://review.openstack.org/#/c/134366/">https://review.openstack.org/#/c/134366/</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I’ve put some comments in reply, and I’m going to attempt to capture the various ideas here. I hope we can discuss this at the Mid-Cycle in Austin.<o:p></o:p></p>
<p class="MsoNormal">1) The existing reset-state python-cinderclient command should not change in unexpected ways and shouldn’t have any new parameters (general consensus here). It should not fail if the driver does not implement my proposed changes (my opinion).<o:p></o:p></p>
<p class="MsoNormal">2) The existing reset-state is broken for some use cases (my UseCase2, for example, when stuck in ‘attaching’ but volume is still attached to instance). Existing reset-state will work for other situations (my UseCase1, when stuck in ‘attaching’
but not really attached.<o:p></o:p></p>
<p class="MsoNormal">3)MikeP pointed out that moving _reset_status() would break clients. I could use help with understanding some of the API code here.<o:p></o:p></p>
<p class="MsoNormal">4) Xing had noted that this doesn’t fix Nova. I hope we can do that separately, since this is proving contentious enough. Some cases such as a timeout during initialize_connection() could be fixed in Nova with a bug once this change is
in. Other Nova changes might require a new Nova API to call for cleanup during reset-state, and that sounds much more difficult to get through the Nova change process.<o:p></o:p></p>
<p class="MsoNormal">5) Walt suggested a new driver method reset_state(). This seems fine, although I had hoped terminate_connection() and detach_volume() would cover all possible cleanup in the driver.<o:p></o:p></p>
<p class="MsoNormal">6) MikeP pointed out that difficulty of getting 30+ drivers to implement a change. I hope that this can be done in such a way that the reset-state commands works exactly as it does today if this is not implemented in the driver. Putting
code in the driver to improve what exists today would be strictly optional.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks again. See you in Austin.<o:p></o:p></p>
<p class="MsoNormal">scottda<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>