openstack
/
puppet-openstack-cookiecutter
Code Issues Proposed changes
Cookiecutter template for a compliant OpenStack puppet-modules
140 Commits 1 Branch 0 Tags 1.7 MiB
Puppet 40%
Ruby 37.5%
Shell 10.8%
Python 10.5%
Pascal 1.2%
Go to file
ZhongShengping 8d238689a2 Switch jobs to Zuul v3 
Change-Id: I18af487194200b16c9ca20578936f885d95b13a6
Depends-On: I9f4bb7c93a31b64285ab1342e8ade20320ed172a
 		2018-02-13 00:28:01 +00:00
contrib Handle unset git information 2017-11-03 16:55:52 -06:00
puppet-{{cookiecutter.project_name}} Remove pinned versions from test-requirements.txt 2018-01-16 14:17:23 +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
.zuul.yaml Switch jobs to Zuul v3 2018-02-13 00:28:01 +00: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
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
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 Switch puppet vertion to 4.8 for unit test 2018-02-12 16:18:20 +08:00

README.md

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.