Cookiecutter template for a compliant OpenStack puppet-modules
Go to file
ZhongShengping 4cbb48893e Configure *_domain_name to Default by default
Keystone v2.0 API was removed so we have no choice but configuring
user_domain_name and project_domain_name otherwise it fallbacks to
Keystone v2.0 and it fails. This patch sets the default value so we make
sure Keystone v3 will be used out of the box for our users.

Change-Id: Icaac286dc98d4df6146b5124dc66b703c8e5086a
2017-10-13 14:39:00 +08:00
contrib Fix path and default year 2017-06-23 14:39:25 +02:00
puppet-{{cookiecutter.project_name}} Configure *_domain_name to Default by default 2017-10-13 14:39:00 +08:00
.gitignore Add .gitignore and cleanup in functions 2016-08-03 17:46:40 -04:00
.gitreview Add .gitreview configuration 2015-06-26 18:03:07 +02:00
bindep.txt Move other-requirements.txt to bindep.txt 2016-08-12 21:09:45 +02:00
cookiecutter.json cookiecutter.json: bump to 2016 2016-01-02 08:06:56 -05:00
functions Add .gitignore and cleanup in functions 2016-08-03 17:46:40 -04:00
LICENSE Initial commit 2015-05-21 21:11:28 +02:00
README.md Update to the latest address in README 2017-09-21 12:02:40 +08:00
run_beaker_tests.sh Add CI scripts 2016-07-26 13:28:09 -04:00
run_lint_tests.sh Add CI scripts 2016-07-26 13:28:09 -04:00
run_syntax_tests.sh run_syntax: use PUPPET_MAJOR_VERSION 2016-07-26 14:57:59 -04:00
run_unit_tests.sh Add CI scripts 2016-07-26 13:28:09 -04:00

Team and repository tags

Team and repository tags

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://git.openstack.org/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.