| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Closes-Bug: #1482986
Change-Id: I72619ef18d24038b46d09e77887d6610ef6e8327
|
|
Partially-Implements: blueprint remove-config-internal
Change-Id: Ic6b7cb217a126c53c0055dbcac4d345583599eb1
|
|
Partially Implements: Blueprint standard-start
Change-Id: I9fa5cc8f6f57b46f8af165778388435b91c28447
|
|
The Liberty release of Cinder will remove the v1 api so we
need to disable it in the cinder_api container and use v2.
Change-Id: I5dab7214d4d39afdf92555e3ffbd7f4a6194cd45
Closes-bug: #1469177
|
|
The log dir and files are being set to nothing and they
were being required by Cinder causing the check to fail.
The log dir and files are not required to run Cinder so
they need to be removed.
Change-Id: I523481f5e3c51a05294fc5e13caaff0a95626f13
Closes-bug: #1468996
|
|
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
|
