Cookiecutter template for a compliant OpenStack puppet-modules
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Tobias Urdin 769f279119 Remove zuul-cloner usage 3 weeks ago
contrib Remove zuul-cloner usage 2 weeks ago
puppet-{{cookiecutter.project_name}} assert_private() params and deps classes 1 month ago
.gitignore Dissuade .gitignore references to personal tools 9 months ago
.gitreview OpenDev Migration Patch 2 months ago
.zuul.yaml Switch jobs to Zuul v3 1 year ago
LICENSE Initial commit 4 years ago Fix Repository 2 months ago
bindep.txt Move other-requirements.txt to bindep.txt 2 years ago
cookiecutter.json cookiecutter.json: bump to 2016 3 years ago
functions Move to opendev 2 months ago Support multiple nodetype library beaker tests 11 months ago Add CI scripts 3 years ago run_syntax: use PUPPET_MAJOR_VERSION 3 years ago Support puppet 4.8 and latest for libraries unit test 1 year ago

Team and repository tags

Team and repository tags


Cookiecutter template for a compliant OpenStack puppet-modules


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


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


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

Remotely (ie. using a git repo)

  1. Run cookiecutter

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.