Add in the ability to override the prefix in .buildconf files removing
the requirement to set the prefix in a .buildconf to limit the number
of images built.
Partially Implements: blueprint refactor-base-image-layout
Change-Id: I1da1559e660adc2fe9eaf5e17ce427c89645a8b7
When an image did not provide a build script, due to a broken link for
instance, the build-all-docker-images script was wrongly marking the
image as "up-to-date", and the functional gate was reporting success.
This commit restores the expected behavior, and mark the images with
non-existent build scripts as failures.
Change-Id: Ifedc8d9c312925fe5aa953ed8f8fdae02b756906
Closes-Bug: #1460959
When we're not providing a tag, the build script will use one based on
the short SHA of the tip of the current git branch.
Make the `build-all-docker-images` script always provide a tag to
`build-docker-image` in order to prevent issues with Docker not being
able to find the base image when changing branches during an ongoing
build.
Closes-Bug: #1458739
Change-Id: Id6925b792f46d14b20a7dbebfaf0d351ddec6538
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
This adds functional tests to tox, along with a number of prerequisite
steps. Since this is primarily a bash project, pbr usage has been avoided.
Tests are to be written in python and put in the tests directory.
Running tox -e setupenv will execute a setup script
(tests/setup_docker.sh) to ensure the running instance of docker meets
the minimum version requirement.
Running tox -e images will execute the image building script
(tools/build-all-docker-images) and will parse the resulting output to report
failures.
Running tox -e startenv will generate the environment file, run
"tools/kolla start", and run first time initialization (eventually).
Running tox -e functional is for actually testing the deployed OpenStack
environment via a series of tests utilizing the client APIs.
Change-Id: Iff6dfdca43f0c44d471e7540a7836e56a0de4507
Change the sed seperator to accept a namespace with a private registry
and add an option to specify the registry. Below is an example for a
registry located at 192.168.0.10:5000.
$ ./build-all-docker-images -r 192.168.0.10:5000
The final image name would be something like this:
'192.168.0.10:5000/kollaglue/centos-rdo-base'
All build, push, and pull commands will still function the same.
Change-Id: Ic0ff96bb8119ddfab15b99e9f1e21cfe8d321dab
Introduce a new --no-use-released-parent option to `build-docker-image`
that allows specifying whether the parent image uses the same tag as
the one that's currently build or the release tag.
Default is to use the release tag for parent image, however
`build-all-docker-images` script forces it to be the current tag.
Change to Dockerfile is coming next.
Change-Id: Ief11c9abb722c181ca85f38ee11800dbf4332a5f
Add "-a" to preserve file attributes so that unnecessary Docker image
build can be avoided. Otherwise, build-all-docker-images will generate
additional image layer due to timestamp change.
Change-Id: I893fa0637937c521198f50b1bba203a27c9f00a3
Closes-Bug: 1449287
By changing the PREFIX variable in the .buildconf one is now able to
build docker images from different bases.
For example, add the following line to your .buildconf file to build
CentOS based images:
PREFIX=centos-rdo-
Default base image is Fedora. For now only RH family is supported.
Additionally, changing the namespace either with the NAMESPACE variable
in .buildconf or via --namespace commandline option now changes the
source namespace as well from the default kollaglue one.
Implements: blueprint multi-baseos
Co-Authored-By: Steven Dake <stdake@cisco.com>
Change-Id: I3964cd2292789ea883a1f2d2738a5731a4fff49b
Make the build scripts work in copies of Kolla so that developers can
continue working while a build is is progress, which can be very long
in the case of build-all-docker-images.
Change-Id: I1b5d9b59ed34dfa622a42495e07d9a1d2ecde86e
Missing quotes around $FORCE_NAMESPACE was causing empty namespace
unless the --namespace switch was passed on the command line.
Change-Id: I474d67e133111bde7935b6f06ff3c8ca0f19d6cb
For some reason -n doesn't work with arrays, probably becuase
the array has an entry by the array's indexed value is empty.
By quoting it we get it as one unit, which behaves as expected.
Change-Id: Ic3243d13d3f8fc9978c460f816e33ad348302d8e
Trap interrupt signal so that the build-all-docker-images script is
stopped on Ctrl-C, and not only the current build.
Additionally, the script now prints a summary of changes on exit.
Change-Id: I3f6ef97d776c7799c73bc709070d97d37406637a
The script is a wrapper for the `build-docker-image` script and thus
respond to the same options. It also responds to two additional `--from`
and `--to` options that allows building only images that have changed
between the specified git revisions.
Examples:
# Build all images contained in docker directory and push new release
build-all-docker-images --release --push
# Build only images modified in test-branch along with their children
build-all-docker-images --from master --to test-branch
Change-Id: Ib83bf475cd2a21965071c13eec4456df5c332edd
