Generate per-element topology/configs. #439
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The generated directory structure looks like this:
Each element has its own fully independant config directory, with copies
of the AD's configs/certs/keys, and a supervisord.conf that lists only
the element. This allows easy deployment of an element on a machine.
There's a common/ subdir at the AD level, for use by sciond and anything
else that needs access to AD-wide config.
Also:
argument, on the command line.
lib.main
, working on them now.lib.main
unit tests added.