On 07/08/15 06:56, Fox, Kevin M wrote:
Heat templates so far seems to be a place to dump examples for showing off how
to use specific heat resources/features.
Are there any intentions to maintain production ready heat templates in it?
Last I asked the answer seemed to be no.
If I misunderstood, heat-templates would be a logical place to put them then.
Historically heat-templates has avoided hosting production-ready
templates, but this has purely been due to having the resources
available to maintain them.
If a community emerged who were motivated to author, maintain and
support the infrastructure which tests these templates then I think they
would benefit from being hosted in the heat-templates repository. It
sounds like such a community is coalescing around the app-catalog project.
Production-ready templates could end up somewhere like
heat-templates/hot/app-catalog. If this takes off then heat-templates
can be assigned its own core team so that more than just heat-core could
approve these templates.
________________________________________
From: Zane Bitter [[email protected]]
Sent: Thursday, August 06, 2015 11:13 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [app-catalog][heat] Heat template contributors repo
On 06/08/15 13:53, Christopher Aedo wrote:
Today during the app-catalog IRC meeting we talked about hosting Heat
templates for contributors. Right now someone who wants to create
their own templates can easily self-host them on github, but until
they get people pointed at it, nobody will know about their work on
that template, and getting guidance and feedback from all the people
who know Heat well takes a fair amount of effort.
What do you think about us creating a new repo (app-catalog-heat
perhaps), and collectively we could encourage those interested in
contributing Heat templates to host them there? Ideally members of
the Heat community would become reviewers of the content, and give
guidance and feedback. It would also allow us to hook into OpenStack
CI so these templates could be tested, and contributors would have a
better sense of the utility/portability of their templates. Over time
it could lead to much more exposure for all the useful Heat templates
people are creating.
Thoughts?
Already exists:
https://git.openstack.org/cgit/openstack/heat-templates/
- ZB
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
