At the moment, Bifrost has caused a few failures which have
blocked the gate, the latest of which is documented in the
bug listed below (alongside with another one that caused another
gate failure).
In order to let patches flow though, we're disabling it
from the gate build checks as agreed on the Kolla meeting on
the 22nd of March 2017. Also, the Ubuntu base image seems
to have a missing /etc/protocols which is created by the
netbase package. This has been added to the base images.
There are issues with subunit getting a very large log all
at once which causes failures that is causing issues. We
also enable logging to a local folder which will make
troubleshooting image builds easier to read and avoid
sending a large blob of data to subunit.
Change-Id: Iee1f8b06ec1066015ea5c6a6a245723402e35a6a
Related-Bug: #1674483
Related-Bug: #1673776
Closes-Bug: #1675101
At the moment, deploy_aio.sh is called with sudo which results
in the environment being wiped. This means that all Zuul
environment variables are removed and therefore when zuul-cloner
runs to checkout the branch of kolla-ansible, it will always
fallback to master as ZUUL_BRANCH is unset.
This patch removes the global usage of sudo in the tox.ini file
as there is existing usage of sudo in the bash script itself. This
will mean that we will only escalate privileges when needed rather
for the whole script and the environment variables should be passed
on properly resulting in the matching release of kolla-ansible being
checked out.
Closes-Bug: #1673756
Change-Id: I477a843e696be7136c020be6408afea01967879d
There were a few issues blocking Kolla from going up to the
latest version of Docker which is 1.13. Most of these issues
seem to have been addressed by 1.13.1.
This patch updates the version installed by Kolla to 1.13.1
for the testing infrastructure to prevent the following
bug which is causing gate failures:
https://github.com/docker/docker/issues/28336
Change-Id: I0d3569b589ee792c9aa6eaa7c539219fcc784271
Adding -e REGISTRY_PROXY_REMOTEURL=https://registry-1.docker.io to the
docker run command in the start-registry script configures the local
registry as a pull through cache. However, pushing of images to the
local registry fails.
Pushing to a registry configured as a pull-through cache is unsupported.
For more information, reference the proxy section in Docker
Documentation (https://docs.docker.com/registry/configuration/)
Corresponding change to the documentation has been made to the
multinode.rst file in the Kolla-ansible repository
https://review.openstack.org/#/c/426858/
Change-Id: I636912f9958490bf751bfa0f449998c61d273241
Closes-Bug: #1659738
1. ZUUL_REFNAME is used in post and release pipeline.
2. change the tarball name to
<base_distro>-<install_type>-registry-<branch>.tar.gz it is usefull
in tag pipeline. we will get name like:
centos-source-registry-4.0.0.tar.gz
Change-Id: I23b16983d02a5758cb251bed8b026ced992559fe
Added the REGISTRY_PROXY_REMOTEURL parameter to the registry
creation script, so that the registry will mirror images from
Docker Hub (while still being able to host custom-built images).
Updated the Multinode guide to reflect this.
Change-Id: Ib789241fd2947b06fb0dc5732a0bf28431e1403d
Closes-Bug: #1647436
- Remove globals.yml and passwords.yml files.
- The gate was still using these files from the kolla
directory. Modified the gate to prevent using these files
from the kolla directory.
- Modified the deploy_aio.sh file to populate passwords
in passwords.yml using kolla-ansible.
Change-Id: I1ed7849d54cab6d5a9217dced73327ea13f06636
Closes-Bug: #1653035
16.04 provides the percona-xtrabackup scripts in the main repos, so the
specific percona repo can be removed. Unfortunately, mariadb10.0 does
not build with galera built-in. So until ubuntu packages mariadb10.1,
we will be dependant on the external repos for mariadb with galera
built in.
Labels keys so they are easily identified in the future. In Jinja2 the
comments cannot go inline while generating the list.
Change-Id: I5e6c2f884c8d59bbc574b71ac731d1b4db18b68c
With 4.4 kernel we can use the improved overlay2 driver instead of
btrfs for significantly better performance when creating layers.
Change-Id: I3b0dfd6db5298dfb34ec160eed910ca76feeb423
Use single unified gate script will be helpful to works after the jobs
is done.
Change-Id: Ic0bbeef4b431132b4f992a696dc5e83c43821b91
Closes-Bug: #1647379
Part of plan to have registry-like behavior in deploy gates. First part
is to run docker registry locally. Next one will be pushing built images
to it, tar.gz whole registry (separate per distro and type) and use
publisher jobs to upload whole registry to tarballs.o.o
Change-Id: I81f154fe6ef58ef93815f42496aef382d32f6774
LOC was broken and called out vagrant specifically. This patch
makes LOC work and renames "Vagrant" to "devenv".
Change-Id: I29f930114d3cba17e870437c99eb3cbae6abb251
init-runonce is should be part of kolla-ansible and was
missed in the original Ansible mass removal.
Change-Id: I7f02d86526f3be56be8960270100547512e7a494
* Remove duplicated info between the 'image-building' and 'multinode'
guides regarding deploying a local insecure registry.
* Add a helper script to easily start a local registry in a consistent
way.
* Remove warnings around bugs in older registries, 2.3+ is now the
default
* Remove references to running the local registry on port 4000, this
causes confusion as Docker expects port 5000 by default unless
specified, and registries are not required for all-in-one deployments
anyhow.
TrivialFix
Change-Id: I89f231df09102e3f1d5f21c8a8ca938ea60ae95b
