<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Reposting here since this is mostly user related.<br>
<div class="moz-forward-container"><br>
<br>
-------- Original Message --------
<table class="moz-email-headers-table" border="0" cellpadding="0"
cellspacing="0">
<tbody>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject:
</th>
<td>[openstack-dev] [Heat] Running latest Heat against older
OpenStacks</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
<td>Wed, 22 May 2013 14:46:19 +1200</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
<td>Steve Baker <a class="moz-txt-link-rfc2396E" href="mailto:sbaker@redhat.com"><sbaker@redhat.com></a></td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">Reply-To:
</th>
<td>OpenStack Development Mailing List
<a class="moz-txt-link-rfc2396E" href="mailto:openstack-dev@lists.openstack.org"><openstack-dev@lists.openstack.org></a></td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
<td><a class="moz-txt-link-abbreviated" href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a></td>
</tr>
</tbody>
</table>
<br>
<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
At the Design Summit a number of people mentioned that they would
like to run the latest release of Heat against their own
installation of an older OpenStack release.<br>
<br>
As a project we're not against this in principle, however we don't
currently have the resources to develop or test against anything
other than latest OpenStack (unless by coincidence of the provided
dev environment).<br>
<br>
It would be very useful to us for people to describe their use
cases for running Heat against older OpenStack installations -
feel free to contribute them to this thread.<br>
<br>
We're about to have the beginnings of some Tempest integration
tests[1]. I'd like to suggest that these be used as a coordination
point for testing latest Heat against private installations. For
those running Heat against older OpenStack installations the
following would be done:<br>
- Run the heat tempest tests against your own Heat/OpenStack
environment<br>
- Participate in finding and fixing regressions that appear in
your own environment (bug reports good, failing tempest tests
better, fixes best)<br>
<br>
There are a couple of caveats worth mentioning:<br>
- the transition from our own CloudWatch-lite alarming to
ceilometer might be messy - there might be a limit to how much we
can mitigate the pain<br>
- it seems reasonable for latest heat to depend on the latest
released client libs. Any regressions involving recent client libs
running on older APIs probably need to be taken to those client
projects.<br>
<br>
In the medium to long term we have some roadmap items which have
implications here, including:<br>
- a local installation of Heat configured to point at a public
OpenStack cloud - auth and other quirks of each cloud need to be
handled<br>
- a single installation of Heat which can deploy to multiple
clouds (private and public)<br>
- Heat DSL concepts [2] of Providers and Environments should allow
Heat to change any aspect of its behavior to support older
installations.<br>
<br>
[1]
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a moz-do-not-send="true"
href="https://review.openstack.org/#/q/topic:bp/add-basic-heat-tests,n,z">https://review.openstack.org/#/q/topic:bp/add-basic-heat-tests,n,z</a><br>
[2]
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a moz-do-not-send="true"
href="https://wiki.openstack.org/wiki/Heat/DSL">https://wiki.openstack.org/wiki/Heat/DSL</a>
<br>
</div>
<br>
</body>
</html>