<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 12/04/2013 04:34 PM, Tim Schnell
wrote:<br>
</div>
<blockquote cite="mid:CEC5182B.78CB%25tim.schnell@rackspace.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div>
<div>Hi Heaters,</div>
<div><br>
</div>
<div>We would like to start a dialog on the general direction of
the proposed Heater project:</div>
<div>blueprint: <a moz-do-not-send="true"
href="https://blueprints.launchpad.net/heat/+spec/heat-template-repo">https://blueprints.launchpad.net/heat/+spec/heat-template-repo</a></div>
<div>wiki: <a moz-do-not-send="true"
href="https://wiki.openstack.org/wiki/Heat/htr">https://wiki.openstack.org/wiki/Heat/htr</a></div>
<div><br>
</div>
<div>It is important to us to start the discussion early but
please note that the wiki is still very much a
work-in-progress. I am actively working to clean up the use
cases and the API spec is just to generate discussion, I
expect it to change based on general consensus.</div>
<div><br>
</div>
<div>We currently have 3 options for starting the Heater
project:</div>
<ol>
<li>Start Heater as a Stackforge project with a different core
team that is dedicated to actively working on Heater</li>
<li>Incubate Heater within the Orchestration umbrella using
the existing Heat Core team</li>
<li>Incubate Heater with the Orchestration umbrella, but
create a sub-project team responsible for reviewing and +2s</li>
</ol>
<div>The idea behind creating a separate core team either via
Stackforge or an Orchestration sub-project is so that the
people actively working on Heater can review and iterate more
quickly through code revisions than dumping Heater code
through the already strained Heat review pipeline.</div>
<div><br>
</div>
</div>
</blockquote>
<br>
You likely want the current heat-core on this team as well, to help
provide guidance about how we operate in the Orchestration program.
But yes, the core team is strained already processing existing
review workloads and can't handle a high-velocity change new code
base very easily. The long term solution to this problem is for
more folks to provide reviews and join the heat core team. But that
doesn't help the heatrr case.<br>
<br>
Regards<br>
-steve<br>
<br>
<blockquote cite="mid:CEC5182B.78CB%25tim.schnell@rackspace.com"
type="cite">
<div>
<div>
</div>
<div>We are still ironing out the definition of a schema for
Heater based on the existing use cases in the wiki and we
would very much appreciate any input with regards to the
existing use cases or proposed API spec. In particular, it is
starting to become apparent that a few of the defined schema
are not necessarily related to Heater specifically and may
make good candidates to start a separate discussion on
inclusion in the HOT specification.</div>
<div><br>
</div>
<div>The following things, specifically, would add value to the
HOT specification in general (copied from the wiki if you need
further context):</div>
<div>
<pre style="padding: 9.5px; font-family: Monaco, Menlo, Consolas, 'Courier New', monospace; font-size: 13px; color: rgb(51, 51, 51); border-top-left-radius: 4px; border-top-right-radius: 4px; border-bottom-right-radius: 4px; border-bottom-left-radius: 4px; margin-top: 0px; margin-bottom: 10px; line-height: 20px; word-break: break-all; word-wrap: break-word; white-space: pre-wrap; background-color: rgb(245, 245, 245); border: 1px solid rgba(0, 0, 0, 0.148438); ">application:
name: Wordpress
version: 3.6.1
flavor: Single Linux server with WordPress 3.6.1 and MySQL 5.5
weight: 3
icons:
- href: <a moz-do-not-send="true" rel="nofollow" class="external free" href="https://600861890ddb34a8670a-744765205721eed93c384dae790e86aa.ssl.cf2.rackcdn.com/wordpress-tattoo.png" style="color: rgb(0, 136, 204); text-decoration: none; cursor: pointer; background-image: url(https://wiki.openstack.org/w/skins/strapping/images/lock-icon.png); padding-right: 13px; background-position: 100% 50%; background-repeat: no-repeat no-repeat; ">https://600861890ddb34a8670a-744765205721eed93c384dae790e86aa.ssl.cf2.rackcdn.com/wordpress-tattoo.png</a>
type: default
- href: <a moz-do-not-send="true" rel="nofollow" class="external free" href="https://600861890ddb34a8670a-744765205721eed93c384dae790e86aa.ssl.cf2.rackcdn.com/wordpress-icon-20x20.png" style="color: rgb(0, 136, 204); text-decoration: none; cursor: pointer; background-image: url(https://wiki.openstack.org/w/skins/strapping/images/lock-icon.png); padding-right: 13px; background-position: 100% 50%; background-repeat: no-repeat no-repeat; ">https://600861890ddb34a8670a-744765205721eed93c384dae790e86aa.ssl.cf2.rackcdn.com/wordpress-icon-20x20.png</a>
type: small
keywords:
- wordpress
- mysql</pre>
</div>
<div>
<pre style="padding: 9.5px; font-family: Monaco, Menlo, Consolas, 'Courier New', monospace; font-size: 13px; color: rgb(51, 51, 51); border-top-left-radius: 4px; border-top-right-radius: 4px; border-bottom-right-radius: 4px; border-bottom-left-radius: 4px; margin-top: 0px; margin-bottom: 10px; line-height: 20px; word-break: break-all; word-wrap: break-word; white-space: pre-wrap; background-color: rgb(245, 245, 245); border: 1px solid rgba(0, 0, 0, 0.148438); ">documentation:
abstract:
some abstract...
guide:
This blueprint includes a single server running Wordpress with Varnish.
This blueprint's performance has not been measured.
instructions:
If you're new to WordPress, the
documentation will step you through the process of logging into the
admin panel, customizing your blog, and changing your theme.</pre>
</div>
<div>Keywords has already been the subject of another mailing
list conversation so let's ignore that one for the moment. If
there is general consensus that we should at least discuss
application, icons, and documentation as possible candidates
for the HOT syntax then I will start a separate mailing list
thread to detail out the use cases.</div>
<div><br>
</div>
<div>The original thought was, other things like template
versioning information and keystone roles for permissions are
very obviously related to Heater. Heater will use those things
to make decisions about how it works. But application
information, icons and documentation are not things that
Heater cares about. Heat also does not care about these things
but the downstream user interface does care about these things
and a human looking at the Heat template would be able to
gather valuable information from these things as well.</div>
<div><br>
</div>
<div>Obviously, the actual structure and use cases for these
things would need to be vetted before inclusion in the HOT
syntax but let's discuss the more general idea that the HOT
syntax should include things that Heat (or Heater) does not
care about but can prove to add real value to the user
experience at some point in a user's interaction with Heat.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Tim</div>
</div>
<div>
<div><br>
</div>
</div>
<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>