On Mon, Jun 29, 2015 at 04:42:00PM -0400, Jay Dobies wrote:
I had originally been thinking of it like slagle describes, from the
child up to the parent as well. What I like about that approach is that
it achieves a more pluggable model when you think about extensions that
aren't accepted or
FWIW, I liked what you were proposing in the other thread. In thinking
about the deployment flow in the Tuskar-UI, I think it would enable
exposing and setting the nested stack parameters easily (you choose
various resources as displayed in a widget, click a reload/refresh
button, and new
We could do likewise in the environment:
resource_registry:
OS::TripleO::ControllerConfig: puppet/controller-config.yaml
...
constraints:
OS::TripleO::ControllerConfig:
- allowed_values:
- puppet/controller-config.yaml,
- foo/other-config.yaml]
These constraints
I had originally been thinking of it like slagle describes, from the
child up to the parent as well. What I like about that approach is that
it achieves a more pluggable model when you think about extensions that
aren't accepted or applicable in TripleO upstream.
If someone comes along and adds
On Fri, Jun 26, 2015 at 03:05:31PM -0400, James Slagle wrote:
On Thu, Jun 25, 2015 at 5:40 PM, Steven Hardy sha...@redhat.com wrote:
On Tue, Jun 23, 2015 at 04:05:08PM -0400, Jay Dobies wrote:
On top of that, only certain templates can be used to fulfill certain
resource types. For
On Thu, Jun 25, 2015 at 5:40 PM, Steven Hardy sha...@redhat.com wrote:
On Tue, Jun 23, 2015 at 04:05:08PM -0400, Jay Dobies wrote:
On top of that, only certain templates can be used to fulfill certain
resource types. For instance, you can't point CinderBackend to
rhel-registration.yaml. That
On Tue, Jun 23, 2015 at 04:05:08PM -0400, Jay Dobies wrote:
I didn't want to hijack Steve Hardy's thread about the recursive validation,
but I wanted to summarize the needs that Tuskar and the UI have been trying
to answer and some of the problems we ran into.
I think it's fairly common
I didn't want to hijack Steve Hardy's thread about the recursive
validation, but I wanted to summarize the needs that Tuskar and the UI
have been trying to answer and some of the problems we ran into.
I think it's fairly common knowledge now that Tuskar and the THT
templates diverged over the
