<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 04/02/2014 08:41 PM, Keith Bray
wrote:<br>
</div>
<blockquote cite="mid:CF624269.24AE9%25keith.bray@rackspace.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div><a moz-do-not-send="true"
href="https://wiki.openstack.org/wiki/Heat/StackMetadata">https://wiki.openstack.org/wiki/Heat/StackMetadata</a></div>
<div><br>
</div>
<div><a moz-do-not-send="true"
href="https://wiki.openstack.org/wiki/Heat/UI">https://wiki.openstack.org/wiki/Heat/UI</a></div>
<div><br>
</div>
<div>-Keith</div>
<div><br>
</div>
</blockquote>
Keith,<br>
<br>
Taking a look at the UI specification, I thought I'd take a look at
adding parameter grouping and ordering to the hot_spec.rst file.
That seems like a really nice constrained use case with a clear way
to validate that folks aren't adding magic to the template for their
custom environments. During that, I noticed it is is already
implemented.<br>
<br>
What is nice about this specific use case is it is something that
can be validated by the parser. For example, the parser could
enforce that parameters in the parameter-groups section actually
exist as parameters in the parameters section. Essentially this
particular use case *enforces* good heat template implementation
without an opportunity for HOT template developers to jam customized
data blobs into the template.<br>
<br>
Stack keywords on the other hand doesn't necessarily follow this
model. I understand the use case, but it would be possible to jam
unstructured metadata into the template. That said, the limitations
on the jamming custom metadata are one deep and it has a clear use
case (categorization of templates for support/UI rendering
purposes).<br>
<br>
I could be wrong, but I think the aversion to a general metadata
section is centered around the problem of different people doing
different things in a non-standardized way.<br>
<br>
I think if we were to revisit the metadata proposal, one thing that
might lead to a more successful outcome is actually defining what
goes in the metadata, rather then allowing the metadata to be
completely free-form as the HOT developer sees fit to implement it.<br>
<br>
For example just taking the keywords proposal:<br>
metadata:<br>
composed_of:<br>
- wordpress<br>
- mysql<br>
architecture:<br>
- lamp<br>
<br>
Even though this metadata can't necessarily be validated, it can be
documented. I definitely have a -2 aversion to free-form metadata
structuring, and am +0 on allowing the information to be declared in
a non-validated way.<br>
<br>
I don't believe the idea of structured metadata based upon real use
cases has really been explored or -2'ed.<br>
<br>
Regards,<br>
-steve<br>
<br>
<blockquote cite="mid:CF624269.24AE9%25keith.bray@rackspace.com"
type="cite">
<div>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt;
text-align:left; color:black; BORDER-BOTTOM: medium none;
BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT:
0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;
BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Lingxian Kong
<<a moz-do-not-send="true"
href="mailto:anlin.kong@gmail.com">anlin.kong@gmail.com</a>><br>
<span style="font-weight:bold">Reply-To: </span>"OpenStack
Development Mailing List (not for usage questions)" <<a
moz-do-not-send="true"
href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, April
2, 2014 9:31 PM<br>
<span style="font-weight:bold">To: </span>"OpenStack
Development Mailing List (not for usage questions)" <<a
moz-do-not-send="true"
href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re:
[openstack-dev] [heat] metadata for a HOT<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"
style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
0 0 5;">
<div>
<div>
<div dir="ltr">
<div class="gmail_default" style="font-family:courier
new,monospace;font-size:small">
Is there any relevant wiki or specification doc?</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">2014-04-03 4:45 GMT+08:00 Mike
Spreitzer <span dir="ltr">
<<a moz-do-not-send="true"
href="mailto:mspreitz@us.ibm.com" target="_blank">mspreitz@us.ibm.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<font face="sans-serif">I would like to suggest that
a metadata section be allowed at the top level of
a HOT. Note that while resources in a stack can
have metadata, there is no way to put metadata on
a stack itself. What do you think?</font><br>
<br>
<font face="sans-serif">Thanks,</font> <br>
<font face="sans-serif">Mike</font><br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr">
<div><b><font
style="background-color:rgb(243,243,243)"
color="#000000" face="courier new,monospace">---------------------------------------</font></b></div>
<div><font color="#0000ff" face="comic sans
ms,sans-serif"><b>Lingxian Kong</b></font></div>
<div><font color="#ff00ff" face="comic sans
ms,sans-serif">Huawei Technologies Co.,LTD.</font></div>
<div><font color="#ff00ff" face="comic sans
ms,sans-serif">IT Product Line CloudOS PDU</font></div>
<div><font color="#ff00ff" face="comic sans
ms,sans-serif">China, Xi'an</font></div>
<div><font color="#ff00ff" face="comic sans
ms,sans-serif">Mobile: +86-18602962792</font></div>
<div><font color="#ff00ff" face="comic sans
ms,sans-serif">Email: <a moz-do-not-send="true"
href="mailto:konglingxian@huawei.com"
target="_blank">
konglingxian@huawei.com</a>; <a
moz-do-not-send="true"
href="mailto:anlin.kong@gmail.com"
target="_blank">
anlin.kong@gmail.com</a></font></div>
</div>
</div>
</div>
</div>
</blockquote>
</span>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</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>
</body>
</html>