| 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
|
|
Change-Id: Ia1bcc94fd58bbfec980bfacbd7acb885a17f9056
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: I07e105a5638ad9fde67e58bf371dffda64563a53
Partially-Implements: blueprint remove-config-internal
|
|
Known bugs/TODOs at this time of this patch update:
https://bugs.launchpad.net/kolla/+bug/1477990
https://bugs.launchpad.net/kolla/+bug/1477993
Implements: Blueprint swift-container
Closes-bug: #1477992
Co-Authored-By: Paul Bourke <paul.bourke@oracle.com>
Change-Id: I031f88a7cd1867104fef12df6ab3ffcc06cb65d6
|
|
Change-Id: I51c042d5947a5f0b30eb8c680ac3a1d97ccc3459
Closes-Bug: #1475155
|
|
These containers look to be broken, bad. Fixing them should be done through a separate bug.
Here we only focus on getting aligned for Ansible deployments.
Partially Implements: Blueprint standard-start
Change-Id: I9d538f2c39510266f30cfed88e01c203f35bfb8e
|
|
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
|
|
The containers don't work, but alteast they will pass the gate ;)
Change-Id: Ic921f982122889d354cfee47772421d147d9ec57
Partially-implements: blueprint bashate-gate
|
|
As a restructure, nothing is changed from the original behaviour and
naming despite the file structure changing. The symlinks to build had
to be updated generating lots of "deleted" and "new_file".
The new structure is:
docker/${base_distro}/${type}/${container}
base_distro == centos, ubuntu, fedora, etc
type == source, binary, rdo
type rdo is a symlink to binary for backwards compatibility
Two new flags are added to the build-all script to support the ability
to support different base distros and a flag to support binary or source
containers.
There are several added folders that are empty to hold the directory
structure for future containers of these types.
To use a prefix other than centos-rdo- you can set PREFIX in the toplevel
directory .buildconf file
Change-Id: Ifc7bac0d827470f506c8b5c004a833da9ce13b90
|
