<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="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:0cm;
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.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-GB">I don’t think this is at use at CERN either. We use Mistral’s cron to schedule the backups if needed.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">Tim<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-left:36.0pt"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">Jim Rollenhagen <jim@jimrollenhagen.com><br>
<b>Date: </b>Tuesday, 20 November 2018 at 16:19<br>
<b>To: </b>"melwittt@gmail.com" <melwittt@gmail.com><br>
<b>Cc: </b>"openstack-discuss@lists.openstack.org" <openstack-discuss@lists.openstack.org><br>
<b>Subject: </b>Re: [openstack-dev] [nova] Can we deprecate the server backup API please?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt">On Tue, Nov 20, 2018 at 5:35 AM melanie witt <<a href="mailto:melwittt@gmail.com">melwittt@gmail.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal" style="margin-left:36.0pt">On Mon, 19 Nov 2018 08:36:40 -0500, Jay Pipes wrote:<br>
> On 11/19/2018 08:15 AM, Matt Riedemann wrote:<br>
>> On 11/18/2018 6:51 AM, Alex Xu wrote:<br>
>>> Sounds make sense to me, and then we needn't fix this strange<br>
>>> behaviour also <a href="https://review.openstack.org/#/c/409644/" target="_blank">
https://review.openstack.org/#/c/409644/</a><br>
>><br>
>> The same discussion was had in the spec for that change:<br>
>><br>
>> <a href="https://review.openstack.org/#/c/511825/" target="_blank">https://review.openstack.org/#/c/511825/</a><br>
>><br>
>> Ultimately it amounted to a big "meh, let's just not fix the bug but<br>
>> also no one really cares about deprecating the API either".<br>
> <br>
> So we'll let the apathy of the past dictate the actions of the future.<br>
<br>
FWIW, my point of view on deprecating the API was/is, if people are <br>
using it to accomplish some task, why deprecate it if it's not hurting <br>
anything else? That is, I didn't want the aforementioned spec to amount <br>
to something like, someone proposes to fix a strange behavior they <br>
observed using the API and our answer is to deprecate the entire API.<br>
<br>
If it's clear that no one is using or benefiting from the API, then I am <br>
in support of deprecating it. But I haven't felt certain about whether <br>
that's the case so far.<br>
<br>
>> The only thing deprecating the API would do is signal that it probably<br>
>> shouldn't be used. We would still support it on older microversions. If<br>
>> all anyone cares about is signalling not to use the API then deprecation<br>
>> is probably fine, but I personally don't feel too strongly about it<br>
>> either way.<br>
> <br>
> Deprecating these kinds of APIs would, as I mentioned in my original<br>
> post, signal that the Nova team is actually serious about cleaning up<br>
> the cruft and getting rid of the debt from years past.<br>
> <br>
> And also that it is serious about Nova not being a dumping ground for<br>
> orchestration and out-of-scope APIs not related to a Compute API.<br>
<br>
That's fair enough, and if we can get a quick confirmation from <br>
operators we know (CERN, NeCTAR, Oath, Vexxhost, OVH, etc) that they <br>
don't use the API, I agree we should go ahead and deprecate it for the <br>
reasons you mention.<o:p></o:p></p>
</blockquote>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt">Oath doesn't have any internal documentation or regression testing around the backup API - I can't guarantee it isn't used, but I think we'd be fine with it going away.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt">// jim<o:p></o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>