Currently source builds and centos-binary builds do not install
rally-openstack. It results in errors with finding openstack plugin.
Change-Id: I26ad81a7076bad7a659e2d80a1ad0453c13794d1
Closes-Bug: #1803968
For Ussuri we decided to follow stable branch tarballs instead of using
release ones. This gives us all fixes just as they land in a repository.
Change-Id: Iff600179630484228fb359417687e3d2a1a8b9f9
Currently pre-commit-hook is failing due to yaml validations using
unversioned python and using non-existent json validations.
Change-Id: I67dc11efe667e2cc67ea1a731edc5c4a03ebd1e7
Closes-Bug: #1778146
CI is set up using Ansible playbooks now.
This also drops redundant shell scripts.
Co-authored-by: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Change-Id: I5264746fd04276448f4668c3bb3a218a40e8660b
The repo is Python 3 now, so update hacking to version 3.0 which
supports Python 3.
Fix problems found by updated hacking version.
Update local hacking checks for new flake8.
Remove hacking and friends from lower-constraints, they are not
needed in installations.
Change-Id: I67e5ca24c550163c218fb06692de0b7c528d8318
We said 'bye' to Python 2 already. So let us use Python 3 for all
scripts.
Unversioned Python binary should be avoided as it may be Python2 or
Python3 (depends on distribution).
Implements: blueprint drop-py2-support
Change-Id: Ifd7912a3debf3ee4ddd8f3e1a4c5870848d4d688
Turned out that linaro-london network pipe is too thin
to support this job. Pushing images took 3 hours so job
timed out.
Will check it once new nodes arrive.
This reverts commit f2801fabdd.
Change-Id: I8897ede43f11090902fe7c0c096f17f57c1c9c67
This time proper approach involves job dependencies.
First we build and publish x86-64 and aarch64 images with architecture
name in image tag. Then we create multiarch manifests to create 'master'
images.
Change-Id: I6b9505dc326636fc6df8798c62c3a5eb1f728a51
This change modifies the CentOS build CI jobs to use a CentOS 8 host
image.
NOTE: This does not affect the version of CentOS used as the base image
in containers built by kolla.
Partially-Implements: blueprint centos-rhel-8
Partially-Implements: blueprint centos-rhel-python3
Change-Id: Ie25b54a4e6116ed2bcb9c3b5c44eb6edbd2e6b49
Removes stuff which does not belong here, along with the docker
daemon systemd service overrides.
Also re-enables IPv6 on CentOS node.
Change-Id: I45238b087647e733544561d333aa560f82e2a07c
TODO: Debian build still requires access to original repo.
Change-Id: Ie4bac5334369a63793d36568a9d3a58a0cdc7667
Signed-off-by: Radosław Piliszek <radoslaw.piliszek@gmail.com>
https://review.opendev.org/#/c/674587/ dropped using of that flag in
deployments. Time to drop it on CI as Debian CI fails when it is
enabled.
Change-Id: I57fa5206f91abcedcd2d526e71e74cf634b81d2c
If stestr failed, then no node info was logged.
Logging node info is now handled in pre and post stages of Zuul.
Additionally Zuul v3 migration recommendations were applied
and some unused code removed improving general readability.
Change-Id: Iae9d37cb76997ba8389e21c7e2a3bf5905abe029
Signed-off-by: Radosław Piliszek <radoslaw.piliszek@gmail.com>
The port of docker registry is conflict with keystone.
So we need to change port of docker registry.
Change-Id: If15c0caf76b5406f590b05030e43d65ca14c8788
Signed-off-by: pengdake <19921207pq@gmail.com>
When building images for binary type, it is expected to not install
executables from untrusted sources, and gem, sensu-install, npm or
pip packages for instance should come from the distro itself.
This commit adds a `validate-binary-build.sh` script that checks for
forbidden commands in the rendered Dockerfile templates for the binary
type builds and hooks this script with the pep8 CI job.
The output is just informative for now until we've fixed the culprit
Dockerfiles, then we'll make the script return an error code and with
the ability to fail the pep8 CI check. This should prevent unwanted
commands from entering binary type Dockerfiles.
Change-Id: I66e54bd18f4256cdca6c0c50626de4f975c246b8
We don't want to use Extended Maintenance (EM) tags, since these are
just markers of a point in time and not available as released artifacts.
Change-Id: If552f7ffc22d4b25769c14c083179eecf5a93158
The current code worked only if the project was using the project_name
in kolla/common/config.py, rather than the tarball_base name. This is
only true on master - on stable branches we may switch to use the
tarball_base name, so the regex won't match.
Change-Id: I839649e6ef662ae3ff320edb3106da818956d26d
We use the stable branch of the requirements project.
Also add an exception for the crane project, which is not managed by
OpenStack releases.
Make use of 'tarball_base' field to handle tarball renames.
Change-Id: I05186d9a3e21615e6b49c62cea83bc4bde4702fe
This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: Ia4ad8d139eb5b37a9e661a789df13ec300eeee6f
Currently CentOS gates use btrfs storage driver and
create /docker device backing btrfs.
This patch is to sync the gate run with Ubuntu.
(post-Trusty) does not use btrfs, only overlay2.
Change-Id: Ic5caa8cf0271b21f71f03fd33c35b3c7bc93ccf4
The mkdir instruction tries to create the
/etc/systemd/system/docker.service.d folder wich in some cases might
not exists. This change includes hte -p argument.
Change-Id: Ia278a2c4dd50a2e57a93b568d0c415e9451fc51f