openstack-infra
/
puppet-docker_registry
Code Issues Proposed changes
puppet-docker_registry/README.md

2.1 KiB
Raw Blame History

docker_registry

Table of Contents

  1. Overview - What is the docker_registry module?
  2. Module Description - What does the module do?
  3. Setup - The basics of getting started with docker_registry
  4. Implementation - An under-the-hood peek at what the module is doing
  5. Limitations - OS compatibility, etc.
  6. Development - Guide for contributing to the module
  7. Contributors - Those with commits

Overview

The docker_registry module is a part of OpenStack-infra, an effort by the OpenStack infrastructure team to provide continuous integration testing and code review for OpenStack-infra projects.

Module Description

The docker_registry module is a thorough attempt to make Puppet capable of managing the entirety of docker_registry. This includes manifests to provision the expected features of this module. Types are shipped as part of the docker_registry module to assist in manipulation of configuration files.

Setup

Installing docker_registry

docker_registry is not currently in Puppet Forge, but is anticipated to be added soon.  Once that happens, you'll be able to install docker_registry with:
puppet module install openstack-infra/docker_registry

Beginning with docker_registry

To utilize the docker_registry module's functionality please check the README.

Implementation

docker_registry

docker_registry is a combination of Puppet manifests to delivery configuration and extra functionality through types and providers.

Beaker-Rspec

This module has beaker-rspec tests

To run the tests on the default vagrant node:

bundle install
bundle exec rake acceptance

For more information on writing and running beaker-rspec tests visit the documentation:

Development

Developer documentation for the entire puppet-infra project.