Open Stack

On 8.9.2015 13:47, Jiří Stránský wrote:
> Apart from "cinder" and "neutron-ml2" directories, we could also have a
> "combined" (or sth similar) directory for env files which combine
> multiple other env files. The use case which i see is for extra
> pre-deployment configs which would be commonly used together. E.g.
> combining Neutron and Horizon extensions of a single vendor [4].

Ah i mixed up two things in this paragraph -- env files vs. extraconfig 
nested stacks. Not sure if we want to start namespacing the extraconfig 
bits in a parallel manner. E.g. 
"puppet/extraconfig/pre_deploy/controller/cinder", 
"puppet/extraconfig/pre_deploy/controller/neutron-ml2". It would be 
nice, especially if we're sort of able to map the extraconfig categories 
to env file categories most of the time. OTOH the directory nesting is 
getting quite deep there :)

J.

> [4]
> https://review.openstack.org/#/c/213142/1/puppet/extraconfig/pre_deploy/controller/all-bigswitch.yaml