Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

2017-11-10 Thread Ben Nemec
On 11/10/2017 03:20 AM, Giulio Fidente wrote: On 11/26/2015 03:17 PM, Jiří Stránský wrote: On 26.11.2015 14:12, Jiří Stránský wrote: [...] It seems TripleO is hitting similar composability and sanity limits with the top-down approach, and the number of parameters which can only be fed via

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

2017-11-10 Thread Bogdan Dobrelya
On 11/10/17 10:20 AM, Giulio Fidente wrote: On 11/26/2015 03:17 PM, Jiří Stránský wrote: On 26.11.2015 14:12, Jiří Stránský wrote: [...] It seems TripleO is hitting similar composability and sanity limits with the top-down approach, and the number of parameters which can only be fed via

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

2017-11-10 Thread Giulio Fidente
On 11/26/2015 03:17 PM, Jiří Stránský wrote: > On 26.11.2015 14:12, Jiří Stránský wrote: [...] >> It seems TripleO is hitting similar composability and sanity limits with >> the top-down approach, and the number of parameters which can only be >> fed via parameter_defaults is increasing. (The

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

2015-12-09 Thread Jiri Tomasek
On 11/25/2015 03:17 PM, Jay Dobies wrote: I think at the same time we add a mechanism to distinguish between internal and external parameters, we need to add something to indicate required v. optional. With a nested stack, anything that's not part of the top-level parameter contract is

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

2015-12-04 Thread Ben Nemec
On 11/20/2015 06:05 PM, Ben Nemec wrote: > Thinking about this some more makes me wonder if we need a sample config > generator like oslo.config. It would work off something similar to the > capabilities map, where you would say > > SSL: > templates: >

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

2015-11-26 Thread Jiří Stránský
My personal preference is to say: 1. Any templates which are included in the default environment (e.g overcloud-resource-registry-puppet.yaml), must expose their parameters via overcloud-without-mergepy.yaml 2. Any templates which are included in the default environment, but via a "noop"

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

2015-11-26 Thread Jiří Stránský
On 26.11.2015 14:12, Jiří Stránský wrote: My personal preference is to say: 1. Any templates which are included in the default environment (e.g overcloud-resource-registry-puppet.yaml), must expose their parameters via overcloud-without-mergepy.yaml 2. Any templates which are included in

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

2015-11-25 Thread Dan Prince
On Thu, 2015-11-19 at 16:16 +, Steven Hardy wrote: > On Mon, Nov 16, 2015 at 08:15:48PM +0100, Giulio Fidente wrote: > > On 11/16/2015 04:25 PM, Steven Hardy wrote: > > > Hi all, > > > > > > I wanted to start some discussion re $subject, because it's been > > > apparrent > > > that we have a

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

2015-11-25 Thread Dan Prince
On Fri, 2015-11-20 at 16:53 +0100, Jiri Tomasek wrote: > On 11/16/2015 04:25 PM, Steven Hardy wrote: > > Hi all, > > > > I wanted to start some discussion re $subject, because it's been > > apparrent > > that we have a lack of clarity on this issue (and have done ever > > since we > > started

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

2015-11-25 Thread Ben Nemec
On 11/25/2015 09:13 AM, Dan Prince wrote: > On Fri, 2015-11-20 at 16:53 +0100, Jiri Tomasek wrote: >> On 11/16/2015 04:25 PM, Steven Hardy wrote: >>> Hi all, >>> >>> I wanted to start some discussion re $subject, because it's been >>> apparrent >>> that we have a lack of clarity on this issue (and

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

2015-11-25 Thread Jay Dobies
I think at the same time we add a mechanism to distinguish between internal and external parameters, we need to add something to indicate required v. optional. With a nested stack, anything that's not part of the top-level parameter contract is defaulted. The problem is that it loses information

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

2015-11-24 Thread Ben Nemec
On 11/23/2015 01:20 AM, Juan Antonio Osorio wrote: > > > On Sat, Nov 21, 2015 at 2:05 AM, Ben Nemec > wrote: > > Thinking about this some more makes me wonder if we need a sample config > generator like oslo.config. It would work

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

2015-11-24 Thread Ben Nemec
On 11/23/2015 06:58 AM, Jay Dobies wrote: > On 11/20/2015 07:05 PM, Ben Nemec wrote: >> Thinking about this some more makes me wonder if we need a sample config >> generator like oslo.config. It would work off something similar to the >> capabilities map, where you would say >> >> SSL: >>

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

2015-11-23 Thread Jay Dobies
On 11/20/2015 07:05 PM, Ben Nemec wrote: Thinking about this some more makes me wonder if we need a sample config generator like oslo.config. It would work off something similar to the capabilities map, where you would say SSL: templates: -puppet/extraconfig/tls/tls-cert-inject.yaml

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

2015-11-22 Thread Juan Antonio Osorio
On Sat, Nov 21, 2015 at 2:05 AM, Ben Nemec wrote: > Thinking about this some more makes me wonder if we need a sample config > generator like oslo.config. It would work off something similar to the > capabilities map, where you would say > > SSL: > templates: >

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

2015-11-20 Thread Jiri Tomasek
On 11/16/2015 04:25 PM, Steven Hardy wrote: Hi all, I wanted to start some discussion re $subject, because it's been apparrent that we have a lack of clarity on this issue (and have done ever since we started using parameter_defaults). Some context: - Historically TripleO has provided a

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

2015-11-20 Thread Ben Nemec
Thinking about this some more makes me wonder if we need a sample config generator like oslo.config. It would work off something similar to the capabilities map, where you would say SSL: templates: -puppet/extraconfig/tls/tls-cert-inject.yaml output: -environments/enable-ssl.yaml

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

2015-11-19 Thread Jay Dobies
My personal preference is to say: 1. Any templates which are included in the default environment (e.g overcloud-resource-registry-puppet.yaml), must expose their parameters via overcloud-without-mergepy.yaml 2. Any templates which are included in the default environment, but via a "noop"

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

2015-11-19 Thread Steven Hardy
On Mon, Nov 16, 2015 at 08:15:48PM +0100, Giulio Fidente wrote: > On 11/16/2015 04:25 PM, Steven Hardy wrote: > >Hi all, > > > >I wanted to start some discussion re $subject, because it's been apparrent > >that we have a lack of clarity on this issue (and have done ever since we > >started using

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

2015-11-19 Thread Juan Antonio Osorio
On Thu, Nov 19, 2015 at 6:16 PM, Steven Hardy wrote: > On Mon, Nov 16, 2015 at 08:15:48PM +0100, Giulio Fidente wrote: > > On 11/16/2015 04:25 PM, Steven Hardy wrote: > > >Hi all, > > > > > >I wanted to start some discussion re $subject, because it's been > apparrent > > >that

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

2015-11-19 Thread Steven Hardy
On Thu, Nov 19, 2015 at 06:50:35PM +0200, Juan Antonio Osorio wrote: >On Thu, Nov 19, 2015 at 6:16 PM, Steven Hardy wrote: > > On Mon, Nov 16, 2015 at 08:15:48PM +0100, Giulio Fidente wrote: > > On 11/16/2015 04:25 PM, Steven Hardy wrote: > > >Hi all, >

[openstack-dev] [tripleo] When to use parameters vs parameter_defaults

2015-11-16 Thread Steven Hardy
Hi all, I wanted to start some discussion re $subject, because it's been apparrent that we have a lack of clarity on this issue (and have done ever since we started using parameter_defaults). Some context: - Historically TripleO has provided a fairly comprehensive "top level" parameters

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

2015-11-16 Thread Giulio Fidente
On 11/16/2015 04:25 PM, Steven Hardy wrote: Hi all, I wanted to start some discussion re $subject, because it's been apparrent that we have a lack of clarity on this issue (and have done ever since we started using parameter_defaults). [...] How do people feel about this example, and others

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

2015-11-16 Thread Jay Dobies
Hi all, I wanted to start some discussion re $subject, because it's been apparrent that we have a lack of clarity on this issue (and have done ever since we started using parameter_defaults). Some context: - Historically TripleO has provided a fairly comprehensive "top level" parameters