Merge lp:~thedac/openstack-mojo-specs/rendered into lp:openstack-mojo-specs
Status: | Work in progress |
---|---|
Proposed branch: | lp:~thedac/openstack-mojo-specs/rendered |
Merge into: | lp:openstack-mojo-specs |
Diff against target: |
680 lines (+515/-1) 30 files modified
helper/tests/simple_os_checks.py (+0/-1) rendered/POC_README.md (+30/-0) rendered/base/SPEC_INFO.txt (+1/-0) rendered/bundle-merge.py (+61/-0) rendered/collect (+17/-0) rendered/example_override_stage/collect (+18/-0) rendered/example_override_stage/manifest (+25/-0) rendered/example_stage/stage-bundle-overrides.yaml (+8/-0) rendered/example_stage/stage-collect (+2/-0) rendered/example_stage/stage-collect-manifest (+2/-0) rendered/example_stage/stage-operations-manifest (+3/-0) rendered/example_stage/stage-validation-manifest (+3/-0) rendered/ha/SPEC_INFO.txt (+12/-0) rendered/ha/preflight.py (+41/-0) rendered/ha/stage-bundle-overrides.yaml (+117/-0) rendered/juju-wait.sh (+6/-0) rendered/l3ha/SPEC_INFO.txt (+3/-0) rendered/l3ha/preflight.py (+33/-0) rendered/l3ha/stage-bundle-overrides.yaml (+11/-0) rendered/l3ha/stage-validation-manifest (+2/-0) rendered/manifest (+37/-0) rendered/preflight.py (+36/-0) rendered/render.sh (+22/-0) rendered/setup-manifest (+8/-0) rendered/ssl/SPEC_INFO.txt (+1/-0) rendered/ssl/stage-bundle-overrides.yaml (+8/-0) rendered/stage-collect-manifest (+1/-0) rendered/stage-operations-manifest (+1/-0) rendered/stage-validation-manifest (+1/-0) rendered/validation-manifest (+5/-0) |
To merge this branch: | bzr merge lp:~thedac/openstack-mojo-specs/rendered |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
OpenStack Charm Testing Maintainers | Pending | ||
Review via email: mp+319489@code.launchpad.net |
Description of the change
Master bundle render proof of concept spec
The rendered specs demonstrate a method to render a collected bundle on the
fly for a mojo spec.
Highlights:
* Bundles, utilities and helpers can all be collected from upstream sources in
flight and used by the mojo spec. Bundles can be rendered from a master source
and merged with stage specific overrides. This will include the ability to add
HA vip overrides.
* This method significantly reduces duplication in individual spec directories.
Only what is needed to override the defaults is required in the stage
directory. The rendered top level directory is not quite as "clean" but it
reduces redundancy and the need for sym links (almost) entirely.
* This method leverages mojo's search path algorithm which checks the most
specific to least specific and overrides with the most specific configuration,
manifest or script file.
* This method leverages mojo's manifest file inclusion capabilities to define
discrete repeatable multi-step processes that can be shared by all stages or
overridden as required.
* This method can also live side by side with the sym link versions until all are
converted.
Unmerged revisions
- 308. By David Ames
-
Use render bundle tool
- 307. By David Ames
-
Generic names for specs
As we will be generating on the fly next or stable soures. We do not need
to name specs next_* or stable_*.Add ssl spec
- 306. By David Ames
-
HA with VIPs from the environment
- 305. By David Ames
-
Master bundle render proof of concept spec