Takashi Kajinami e4862af5dc Drop hard-coded log_file
Because the service config file is shared among multiple services,
we should not set the option without any specific reason. In case
the option is not set (and no --log-file argument is passed) then
log file name is determined according to the process name, and each
service creates its own file.

Change-Id: Iadaf4eceb0a052bef437603d6cbe6422f4ee9b13
2024-09-22 12:33:37 +09:00
2019-04-19 19:29:14 +00:00
2018-02-13 00:28:01 +00:00
2022-08-16 05:38:12 +00:00
2015-05-21 21:11:28 +02:00
2020-09-17 01:03:49 +02:00
2016-07-26 13:28:09 -04:00
2020-09-19 00:14:23 +02:00
2019-10-10 11:33:04 +02: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://opendev.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.

Description
Cookiecutter template for a compliant OpenStack puppet-modules
Readme 1.7 MiB
Languages
Puppet 39.9%
Ruby 37.5%
Shell 10.8%
Python 10.6%
Pascal 1.2%