4 Commits

Author SHA1 Message Date
Ben Nemec
d69940d5af Fix env-generator doc formatting
Bulleted lists must have whitespace before and after or they don't
render properly.

Change-Id: I7dcc58b8d9e02d99918bbdcc7d0fc3905d66f71c
2017-09-06 16:29:44 -05:00
Ben Nemec
204a582099 Add nested sample environments for inject-trust-anchor
Fix a bug that prevented these working.  A unit test and
documentation for the nested environment functionality is also
included.

Change-Id: I2d4aeb584eb624178d601cfd6bc0a6473cb5289f
2017-06-12 15:02:50 -05:00
Ben Nemec
f503d1b0e7 Support config dir for env generator input files
We're not going to want to list every single sample environment in
a single file, so let's also take a directory and just read every
yaml file in it.  This commit adds support for that as well as
some initial environments to demonstrate its use.

Change-Id: If2c608f2a61fc5e16784ab594d23f1fa335e1d3c
2017-06-12 15:02:50 -05:00
Ben Nemec
4e24c8cb6a Sample environment generator
This is a tool to automate the generation of our sample environment
files.  It takes a yaml file as input, and based on the environments
defined in that file generates a number of sample environment files
from the parameters in the Heat templates.  A tox genconfig target
is added that mirrors how the other OpenStack services generate
their sample config files.

A description of the available options for the input file is
provided in a README file in the sample-env-generator directory.

In this commit only a single sample config is provided as a basic
example of how the tool works, but subsequent commits will add
more generated sample configs.

Change-Id: I855f33a61bba5337d844555a7c41b633b3327f7a
bp: environment-generator
2017-06-12 15:02:50 -05:00