<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<base href="x-msg://1013/">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
Randall,
<div><br>
</div>
<div>No, they are related, but different. I linked them. Yours involves the creation of a repo, mine involves a client feature to use the repo, or specify an alternate, obviating the need to specify an explicit template file, but letting you use a name for
the template so it would work more like "pip install <whatever>".
<div><br>
</div>
<div>Adrian<br>
<div><br>
<div>
<div>On Apr 24, 2013, at 12:08 PM, Randall Burt <<a href="mailto:randall.burt@RACKSPACE.COM">randall.burt@RACKSPACE.COM</a>></div>
<div> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div style="font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">
<div>Does your hot repo overlap with my Heater blueprint?<br>
<br>
<br>
-------- Original message --------<br>
From: Adrian Otto <<a href="mailto:adrian.otto@rackspace.com">adrian.otto@rackspace.com</a>><span class="Apple-converted-space"> </span><br>
Date: 04/24/2013 2:00 PM (GMT-06:00)<span class="Apple-converted-space"> </span><br>
To: OpenStack Development Mailing List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><span class="Apple-converted-space"> </span><br>
Subject: Re: [openstack-dev] [Heat] Template repository location (infra guidance needed)<span class="Apple-converted-space"> </span><br>
<br>
<br>
</div>
<font size="2"><span style="font-size: 10pt; ">Steven,<br>
<br>
On Apr 24, 2013, at 11:00 AM, Steven Hardy <<a href="mailto:shardy@redhat.com">shardy@redhat.com</a>><br>
wrote:<br>
<br>
> On Wed, Apr 24, 2013 at 04:20:18PM +0000, Adrian Otto wrote:<br>
>> Steven,<br>
>> <br>
>> I don't think we need to use Stackforge at all anymore. Heat is integrated. Let's keep things simple, and use the Heat repo for Heat's work product. The way I see it is that if an OpenStack dev is creating a template as part of a Heat development effort,
then the artifacts relating to that work belong in OpenStack.<br>
> <br>
> Well this is basically what I was thinking when we were discussing<br>
> stackforge in the team, hence my question when starting this thread.<br>
> <br>
> I agree that ideally this will be hosted under the openstack org (I'd<br>
> prefer this to stackforge if possible), but "the Heat repo" implies the<br>
> main openstack/heat repo, which I would prefer to decouple from example<br>
> templates, since they are example inputs not implementation (e.g it doesn't<br>
> make sense for users to have to install the service implementation to get<br>
> access to the example templates when Heat is packaged)<br>
<br>
That sounds to me like a documentation concern. I think that can be addressed using the WIKI.<br>
<br>
We should have some number of functional templates that are used to demonstrate and test Heat, and those belong in any Heat package.<br>
<br>
>> We may want to consider a future setup where there is a central community repository where best practices for deployment of various applications and systems can be expressed as templates and stored in a registry or repo that can be browsed by OpenStack users.
Think CPAN, or PIP. This is where templates could go that are not part of a coordinated release. That may or not belong in OpenStack, but I think that's actually a separate discussion.<br>
> <br>
> Agree, this sounds like a good future idea but out of scope for the main<br>
> Heat project, I'm keen that we just have a reasonable number of tested<br>
> examples to demonstrate our functionality.<br>
<br>
The maintenance of the repo may be out of scope, but I think a feature in Heat to enable this is worth consideration. I registered a blueprint accordingly:<br>
<br>
<a href="https://blueprints.launchpad.net/heat/+spec/hot-repo">https://blueprints.launchpad.net/heat/+spec/hot-repo</a><br>
<br>
Adrian<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</span></font>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</body>
</html>