| Age | Commit message (Collapse) | Author | Files | Lines |
|
Remove the docker directory (yay) and old build tools.
This will result in an f21 failing gate - however, I have a patch
submission to remove that gate from our project configuration.
Change-Id: I3c461cedb6906422c8076f60c470e773d6cdcf33
Partially-Implements: blueprint remove-docker-dir
|
|
Remove all data containers from the repository except the one image
we intend to reuse for each data container. Adjust compose files to
remove all references to the unique data containers which serve no
purpose other then to take up extra resources.
Needs VOLUME in data containers exported in the compose files.
Change-Id: Id7746110946ef9836180cf57302aaf827e7e5405
Partially-Implements: blueprint one-data-container
|
|
Change-Id: I15a9c34a08055c6f9ad53f211a8c1a62de3f58ff
Partially-Implements: blueprint remove-config-internal
|
|
designate added tooz as dependency, but this is not reflected in package
installation, so workaround this by yum install python-tooz
Change-Id: Ia1b69d3feb7379131371db75a25eefb949a66758
Closes-Bug: #1476578
|
|
Partially Implements: Blueprint standard-start
Change-Id: I96342c3bdb99d317ce75e0bbb78bdf469f9d1bf7
|
|
All start.sh scripts should be in docker/common directory
instead of docker/centos.
Change-Id: Ifc1d07246e3b56156a1dc861e2b262f75c1cd918
Closes-Bug: #1467528
|
|
The only files in the docker image directories that differ majorly between
distros are the Dockerfiles (e.g. different package manager mechanisms,
different repo sources, etc).
The supporting files such as the start.sh/check.sh and config files should
largely stay the same between base images.
This change moves these files up into a "common" directory, and symlinks them
in the same way that the build script is managed. This means when adding a new
base distro only new Dockerfiles need to be created. Also, if a distro does
happen to require a vastly different start.sh script for example, one can
choose to simply not symlink to the common and instead drop in a custom one.
Implements: blueprint refactor-base-image-layout
Change-Id: Ic4db69d31ff54a1fb95af4853a2e5ae490064284
|
|
Container for Designate Sink, automatic domain creation for
enabled notification handlers (nova and/or neutron).
Change-Id: I41118cb149e7f39a17bff49123d82905b51b7939
Blueprint: designate-container
|
|
Change-Id: I14eec402d4e9afbfc58b74938df01c858314e6f3
Closes-bug: #1462798
|
|
This is a complete DNS solution, with hidden master and bind9 slave.
It lacks the designate-sink service, because there is no true specification
to implement that. It listens for Nova/Neutron events and creates records
though adding those to just 1 domain isn't helping much in an environment
with multiple tenants.
Change-Id: I500fb6058b118d25a4ccfd1d3479830c36af7e2a
Blueprint: designate-container
|