kayobe/ansible/roles/docker-registry
Mark Goddard 4038c8226b Change reserved keyword 'action' to 'kayobe_action'
For several roles (cadvisor, inspection-store, docker-registry, etc.),
we use an 'action' variable, in a similar manner to kolla-ansible,
to determine the current action being performed (deploy,
reconfigure, upgrade). It is likely this information will be
useful for custom playbooks, so we should expose it. The 'action'
keyword is reserved, and its use triggers a warning, so we change its
name to kayobe_action before advertising it to users.

Change-Id: I5ffbb8b014a31e27141bfc8bf780297d81c840be
Story: 2001663
Task: 12604
2018-05-21 16:00:57 +01:00
..
defaults Change reserved keyword 'action' to 'kayobe_action' 2018-05-21 16:00:57 +01:00
tasks Change reserved keyword 'action' to 'kayobe_action' 2018-05-21 16:00:57 +01:00
README.md Update python docker package requirement note in role READMEs 2017-12-13 17:03:54 +00:00

README.md

Docker Registry

This role can be used to configure a Docker registry running in a Docker container.

Requirements

The host executing the role has the following requirements:

  • Docker engine
  • Python docker >= 2.0.0

Role Variables

docker_registry_enabled: Whether the Docker registry is enabled. Defaults to true. docker_registry_namespace: Docker image namespace. Defaults to library. docker_registry_image: Docker image name. docker_registry_tag: Docker image tag. Defaults to latest. docker_registry_image_full: Full docker image specification. docker_registry_restart_policy: Docker restart policy for docker_registry container. Defaults to unless-stopped. docker_registry_restart_retries: Number of Docker restarts. Defaults to 10.

Dependencies

None

Example Playbook

The following playbook configures a Docker registry.

---
- hosts: docker-registry
  roles:
    - role: stackhpc.docker-registry

Author Information