Mark Goddard 56ee18d0fd Add configuration to deploy a Docker registry on a controller

By default the registry listens on port 4000 to avoid clashing with keystone.
It is configured via the following commands:

kayobe overcloud service <deploy|pull|reconfigure|upgrade>

2017-06-27 18:49:10 +01:00

1.1 KiB

Raw Blame History

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
docker-py >= 1.7.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

Mark Goddard (mark@stackhpc.com)

1.1 KiB Raw Blame History