We want to default to running all tox environments under python 3, so
set the basepython value in each environment.
We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.
We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.
Change-Id: Ia848da33224b359c3ac0ad5a57cebc1897369f3e
This template needs to stay in project-config to work properly.
also, it's obsolete. project-config is updated already.
Change-Id: I818b10cd6614870fc0673d96d20a9fe66b99ba94
We want to default to running all tox environments under python 3, so
set the basepython value in each environment.
We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.
We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.
Change-Id: Ib81683ef8d3677a567d1e62e1ec6adc9a1ed8ea4
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
With https://review.openstack.org/#/c/597153/
registry_pkg_manager was set to dnf for Centos7 as
well due to wrong string comparison, This patch convert
ansible_distribution_major_version to integer before
comparison and fixes the issue.
Change-Id: I603c1f932c63d07040e6aa24f1a75eab4e389738
Related-Blueprint: dnf-support
In order to run this on python3 and fedora, we need to use the dnf
module or use package.
Change-Id: I9f61facd0165f67af18018dff363a8e2075f3aee
Related-Blueprint: dnf-support
We don't want these roles pushed to pypi, so no need to try uploading them.
This template is the same as publish-to-pypi except it's not pushing the
project to pypy.
Also add jobs from project-config; so we can control here.
Change-Id: I9b2b29b3a79a89199f7d149673791d1711189913
With the README file used as the package long description, errors would
cause the package checks to fail when uploading to PyPi. This switches
the README to be in RST format and gets rid of validation errors.
Change-Id: I8f3d3eb9ba2cc4b3d46d8748bc1340500fc7be0e
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Move the wait-for-registry-up loop and systemd daemon reloading
commands behind the user-faced "restart docker(-registry)"
handlers. So users may just refer to it w/o manual daemon reload
tasks and w/o knowing of other advanced sub-steps details. But
those handlers may still be notified directly as well.
Add a fixed delay of a 10s for the docker service reload handler,
which is nice to have for the loaded systems running that command
way too long.
Add wait-for-docker-service-up loop into the docker service
reload handler for the better failures detection.
Simplify future support on CoreOS/atomic distributions
(which require reloading docker and socket in particular order)
Based on
https://github.com/kubernetes-incubator/kubespray/blob/ \
810596c6d8f1e13afa934ddeef996d4f42b29890/roles/docker/handlers/main.yml
Depends-On: I26cc07aa05912c3e84d59003686eae210e924a16
Change-Id: I28e8c682005e77b87a347f4d2a2dff219fab488c
Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
Validate that Registry is actually up and running.
It's useful to fail early if the registry is for some reasons not
started correctly. It avoids to go further in the deployments steps and
loose time before seeing the failures when deploying containers.
Change-Id: Ic29d1c10741bf946c1df709d14b9b30dcf7f6c9b
The tasks were taken from OpenStack TripleO. They manage the case where
Docker needs to be updated. We'll first stop containers, stop docker
then update the rpm before making sure Docker is running again.
Change-Id: Ibde3d326b7e824fe09fafb9f46875b1e6739d299
So we can actually test changes in this role.
Depends-On: Iee0e08cd48f173a39a6f3a1ea54b29e370d4f334
Change-Id: I75a0683b7b6866f7f4c33fa845a7a88666a22c84
This role should really be focused on creating a working docker and
registry, and installing kolla is not really related to that.
Even in CI, if container modifications are required it is more likely
to happen via modifying existing images with
ansible-role-tripleo-modify-image, which doesn't involve the kolla
package.
Change-Id: I7ba8d89b75f206aa92bdfd907712b1b0b44a4c32
Add support to configure additional sockets with a new parameter (must
be an array):
container_registry_additional_sockets
Example of value:
container_registry_additional_sockets:
- /var/lib/openstack/docker.sock
- /var/run/some-other/docker.sock
Change-Id: I0da7f5f1005532b8ba68c46ed6ca065cc333d0d5
We don't want to automatically enable selinux options, but instead have
control via container_registry_selinux parameter if whether or not we
want to add selinux flags to docker.
This code:
{% if container_registry_mirrors | length > 0 %}registry-mirrors: [{{ container_registry_mirrors }}]{% endif %}
Needs to include the brackets and I haven't found a way yet to include
them without Ansible failure. In the meantime, let's go back on the old
code.
DockerRegistryMirror is given as a string in TripleO, so for now, let's
add (missing) brackets and figure out later how we can change tripleo to
change the data type.
- add prefix to role variable names to avoid name collisions
- use ini_file rather than blockinfile for setting mount flags
- use ansible_selinux fact rather than depending on variable in role
- use role variables for setting values to be used in tasks rather than in line conditionals
- use filters for creating JSON file rather than a template
- remove '---' from YAML files since Ansible does not user YAML front matter
- update meta/main.yml
98k
Zuul
Andreas Jaeger
Doug Hellmann
yatin
Jose Luis Franco Arza
Alex Schultz
Emilien Macchi
Sean McGinnis
Bogdan Dobrelya
Steve Baker
Emilien Macchi
Sam Doran