<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 01/13/2016 10:33 AM, Juan Antonio
Osorio wrote:<br>
</div>
<blockquote
cite="mid:CAG=EsMP57iOgbByDgWe3v9dtaH63hVX7pG_mFttUv70U40GAgw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>IIRC some of them were already marked (via a comment) as
deprecated.<br>
<br>
</div>
+1 to cleaning up the parameters. I think it should be done as
soon as possible, as the existence of some of them makes the
usage of the templates quite confusing.<br>
<br>
</div>
BR<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Jan 12, 2016 at 10:47 PM,
Steven Hardy <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:shardy@redhat.com" target="_blank">shardy@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
I've noticed that we have a fairly large number of unused
parameters in<br>
t-h-t, some of which are marked deprecated, some aren't.<br>
<br>
Since we moved tripleoclient to use parameter_defaults
everywhere, I think<br>
it should be safe to remove these unused parameters, even in<br>
overcloud.yaml.<br>
<br>
See:<br>
<br>
<a moz-do-not-send="true"
href="https://review.openstack.org/#/c/227057/"
rel="noreferrer" target="_blank">https://review.openstack.org/#/c/227057/</a><br>
<br>
<a moz-do-not-send="true"
href="https://review.openstack.org/#/c/227057/"
rel="noreferrer" target="_blank">https://review.openstack.org/#/c/227057/</a><br>
<br>
Since those, we can pass removed/deprecated parameters from
the client and<br>
they will be ignored, even if they're removed from the
template (unlike if<br>
you use "parameters", where a validation error would occur.<br>
<br>
I'd like to go ahead and clean these up (only on the master
branch), is<br>
that reasonable? We can document the change via a mitaka
release note?<br>
<br>
Ideally, we'd have user-visible warnings for a deprecation
period, but<br>
there's no way to output such warnings atm via heat, so we'd
need to wire<br>
them in via tripleoclient or tripleo-common, which seems a
bit backwards<br>
given that we can just remove the parameters there instead.<br>
<br>
Thoughts?<br>
<br>
Steve<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a moz-do-not-send="true"
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
<div class="gmail_signature">
<div dir="ltr">
<div><font style="font-family:arial
narrow,sans-serif;color:rgb(102,102,102)" size="2">Juan
Antonio Osorio R.<br>
e-mail: <a moz-do-not-send="true"
href="mailto:jaosorior@gmail.com" target="_blank">jaosorior@gmail.com</a><br>
</font><font style="font-family:arial
narrow,sans-serif;color:rgb(102,102,102)" size="2"><br>
</font></div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
+1 IUC this will reduce the number of parameters returned by nested
heat validate, which is a good thing as those parameters confuse
user.<br>
<br>
Jirka<br>
</body>
</html>