openstack/puppet-openstack-cookiecutter
Code Issues Proposed changes
Cookiecutter template for a compliant OpenStack puppet-modules
59 Commits 1 Branch 0 Tags 1.7 MiB
Puppet 39.9%
Ruby 37.5%
Shell 10.8%
Python 10.6%
Pascal 1.2%
4c84252925
Go to file
Emilien Macchi 4c84252925 cookiecutter.json: bump to 2016 
Change-Id: Icf87eda6be92921539423947bf9110ed81b99f7f
2016-01-02 08:06:56 -05:00
contrib Handle the postgresql md5password in specs 2015-07-10 18:07:54 +02:00
puppet-{{cookiecutter.project_name}} Make Keystone_endpoint match service by name/type 2015-12-21 19:33:54 +01:00
.gitreview Add .gitreview configuration 2015-06-26 18:03:07 +02:00
cookiecutter.json cookiecutter.json: bump to 2016 2016-01-02 08:06:56 -05:00
LICENSE Initial commit 2015-05-21 21:11:28 +02:00
README.md Update templates to reflect various changes 2015-06-30 13:00:24 +02:00

README.md

puppet-openstack-cookiecutter

Cookiecutter template for a compliant Openstack puppet-modules

Installation

Install cookiecutter either from source, pip or package if it exists

Usage

There are two ways to create the boilerplate for the puppet module.

Locally

  1. Clone locally the puppet-openstack-cookiecutter repository.
  2. Run cookiecutter /path/to/cloned/repo

Remotely (ie. using a git repo)

  1. Run cookiecutter https://github.com/openstack/puppet-openstack-cookiecutter.git

What's next

Once the boilerplate created, in order to be compliant with the other modules, the files managed by msync, (or configs) needs to be in the project folder. Once synced module is ready, announce its existence to the ML, make the proper patch to openstack-infra and finally wait for the reviews to do the rest.