2016-04-01 23:49:54 +00:00
|
|
|
# Auto-generated Puppetfile for Puppet OpenStack project
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
|
2016-04-01 23:49:54 +00:00
|
|
|
## OpenStack modules
|
2015-10-09 00:00:58 +00:00
|
|
|
mod 'aodh',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-aodh',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
2015-10-09 00:00:58 +00:00
|
|
|
|
|
|
|
mod 'barbican',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-barbican',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
2015-10-09 00:00:58 +00:00
|
|
|
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
mod 'ceilometer',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-ceilometer',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
|
2016-01-25 22:50:43 +00:00
|
|
|
mod 'ceph',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-ceph',
|
2016-01-25 22:50:43 +00:00
|
|
|
:ref => 'master'
|
|
|
|
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
mod 'cinder',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-cinder',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
|
2016-10-20 18:59:41 +00:00
|
|
|
mod 'cloudkitty',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-cloudkitty',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
2016-10-20 18:59:41 +00:00
|
|
|
|
2016-06-08 15:04:40 +00:00
|
|
|
mod 'congress',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-congress',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
2016-06-08 15:04:40 +00:00
|
|
|
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
mod 'designate',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-designate',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
|
2016-06-08 15:04:40 +00:00
|
|
|
mod 'ec2api',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-ec2api',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
2016-06-08 15:04:40 +00:00
|
|
|
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
mod 'glance',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-glance',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
|
|
|
|
mod 'gnocchi',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-gnocchi',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
|
|
|
|
mod 'heat',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-heat',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
|
|
|
|
mod 'horizon',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-horizon',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
|
|
|
|
mod 'ironic',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-ironic',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
|
|
|
|
mod 'keystone',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-keystone',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
|
|
|
|
mod 'manila',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-manila',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
|
2015-10-09 00:00:58 +00:00
|
|
|
mod 'mistral',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-mistral',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
2015-10-09 00:00:58 +00:00
|
|
|
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
mod 'monasca',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-monasca',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
|
2015-10-09 00:00:58 +00:00
|
|
|
mod 'murano',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-murano',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
2015-10-09 00:00:58 +00:00
|
|
|
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
mod 'neutron',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-neutron',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
|
|
|
|
mod 'nova',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-nova',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
|
2016-03-09 22:46:04 +00:00
|
|
|
mod 'octavia',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-octavia',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
2016-03-09 22:46:04 +00:00
|
|
|
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
mod 'openstack_extras',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-openstack_extras',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
|
|
|
|
mod 'openstacklib',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-openstacklib',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
|
2016-03-09 22:46:04 +00:00
|
|
|
mod 'oslo',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-oslo',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
2016-03-09 22:46:04 +00:00
|
|
|
|
2016-04-14 01:15:21 +00:00
|
|
|
mod 'ovn',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-ovn',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
2016-04-14 01:15:21 +00:00
|
|
|
|
2016-08-30 19:45:47 +00:00
|
|
|
mod 'panko',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-panko',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
2016-08-30 19:45:47 +00:00
|
|
|
|
2019-01-31 11:55:55 +00:00
|
|
|
mod 'placement',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-placement',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
2019-01-31 11:55:55 +00:00
|
|
|
|
2016-10-20 18:59:41 +00:00
|
|
|
mod 'qdr',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-qdr',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
2016-10-20 18:59:41 +00:00
|
|
|
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
mod 'sahara',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-sahara',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
|
|
|
|
mod 'swift',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-swift',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
|
2017-02-02 16:47:56 +00:00
|
|
|
mod 'tacker',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-tacker',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
2017-02-02 16:47:56 +00:00
|
|
|
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
mod 'tempest',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-tempest',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
|
|
|
|
mod 'trove',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-trove',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
|
|
|
|
mod 'vswitch',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-vswitch',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
|
2017-02-18 08:16:13 +00:00
|
|
|
mod 'vitrage',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-vitrage',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
2017-02-18 08:16:13 +00:00
|
|
|
|
2016-06-08 15:04:40 +00:00
|
|
|
mod 'watcher',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-watcher',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
2016-06-08 15:04:40 +00:00
|
|
|
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
mod 'zaqar',
|
2019-04-21 06:44:50 +00:00
|
|
|
:git => 'https://opendev.org/openstack/puppet-zaqar',
|
2019-10-09 22:51:51 +00:00
|
|
|
:ref => 'stable/train'
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
|
2016-04-01 23:49:54 +00:00
|
|
|
## External modules
|
|
|
|
mod 'powerdns',
|
|
|
|
:git => 'https://github.com/antonlindstrom/puppet-powerdns',
|
|
|
|
:ref => '0.0.5'
|
|
|
|
|
2016-07-31 06:11:18 +00:00
|
|
|
mod 'kmod',
|
|
|
|
:git => 'https://github.com/camptocamp/puppet-kmod',
|
2019-07-31 06:08:07 +00:00
|
|
|
:ref => '2.3.1'
|
2016-07-31 06:11:18 +00:00
|
|
|
|
2016-04-01 23:49:54 +00:00
|
|
|
mod 'sysctl',
|
|
|
|
:git => 'https://github.com/duritong/puppet-sysctl',
|
2018-07-25 06:04:37 +00:00
|
|
|
:ref => 'v0.0.12'
|
2016-04-01 23:49:54 +00:00
|
|
|
|
2017-01-11 15:32:30 +00:00
|
|
|
mod 'ipaclient',
|
|
|
|
:git => 'https://github.com/joshuabaird/puppet-ipaclient',
|
2017-12-07 06:11:19 +00:00
|
|
|
:ref => '2.5.2'
|
2017-01-11 15:32:30 +00:00
|
|
|
|
2016-04-01 23:49:54 +00:00
|
|
|
mod 'staging',
|
|
|
|
:git => 'https://github.com/nanliu/puppet-staging',
|
|
|
|
:ref => '1.0.4'
|
|
|
|
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
mod 'apache',
|
|
|
|
:git => 'https://github.com/puppetlabs/puppetlabs-apache',
|
2019-09-14 06:04:52 +00:00
|
|
|
:ref => 'v5.1.0'
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
|
|
|
|
mod 'apt',
|
|
|
|
:git => 'https://github.com/puppetlabs/puppetlabs-apt',
|
2017-05-17 16:54:47 +00:00
|
|
|
:ref => '2.4.0'
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
|
|
|
|
mod 'concat',
|
|
|
|
:git => 'https://github.com/puppetlabs/puppetlabs-concat',
|
2017-05-17 16:54:47 +00:00
|
|
|
:ref => '2.2.1'
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
|
|
|
|
mod 'firewall',
|
|
|
|
:git => 'https://github.com/puppetlabs/puppetlabs-firewall',
|
2019-09-26 06:12:17 +00:00
|
|
|
:ref => 'v2.1.0'
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
|
|
|
|
mod 'inifile',
|
|
|
|
:git => 'https://github.com/puppetlabs/puppetlabs-inifile',
|
2018-05-02 01:22:19 +00:00
|
|
|
:ref => '2.2.0'
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
|
|
|
|
mod 'mysql',
|
|
|
|
:git => 'https://github.com/puppetlabs/puppetlabs-mysql',
|
2018-10-05 06:19:06 +00:00
|
|
|
:ref => '6.2.0'
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
|
|
|
|
mod 'postgresql',
|
|
|
|
:git => 'https://github.com/puppetlabs/puppetlabs-postgresql',
|
2019-09-14 06:04:52 +00:00
|
|
|
:ref => 'v6.2.0'
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
|
|
|
|
mod 'rabbitmq',
|
|
|
|
:git => 'https://github.com/puppetlabs/puppetlabs-rabbitmq',
|
2019-08-18 06:15:46 +00:00
|
|
|
:ref => 'v9.1.0'
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
|
|
|
|
mod 'rsync',
|
|
|
|
:git => 'https://github.com/puppetlabs/puppetlabs-rsync',
|
2019-02-15 06:06:06 +00:00
|
|
|
:ref => '1.1.1'
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
|
|
|
|
mod 'stdlib',
|
|
|
|
:git => 'https://github.com/puppetlabs/puppetlabs-stdlib',
|
2019-09-21 06:10:38 +00:00
|
|
|
:ref => 'v6.1.0'
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
|
|
|
|
mod 'vcsrepo',
|
|
|
|
:git => 'https://github.com/puppetlabs/puppetlabs-vcsrepo',
|
2019-06-15 06:22:16 +00:00
|
|
|
:ref => 'v3.0.0'
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
|
2019-02-22 17:23:57 +00:00
|
|
|
mod 'git_resource',
|
|
|
|
:git => 'https://github.com/voxpupuli/puppet-git_resource',
|
|
|
|
:ref => 'v1.0.2'
|
|
|
|
|
Add Puppetfile and install script
This repo will be cloned by the puppet modules and used to install
modules in functional tests. The script uses r10k to deploy modules
from the Puppetfile because this is the Puppet Labs recommended way to
manage puppet environments, and it is a popular method among our users.
We install all modules from git, not the forge, because r10k does not
give us dependency resolution so installing from the forge does not buy
us anything. If the modules have stable branches in git, r10k uses the
stable branch as a ref, otherwise it uses a tag (pinning to a specific
release).
If zuul-cloner is available, the script first installs the external
modules with r10k, then extracts the OpenStack modules from the
Puppetfile to install with zuul-cloner. In the future, this part may be
split out into a JJB job.
Note: because r10k purges the modules directory before installing
modules, and this feature cannot be turned off[1], we must run r10k to
install the external modules before running zuul-cloner to install the
OpenStack modules.
[1] https://github.com/puppetlabs/r10k/issues/172
Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015-06-30 23:59:52 +00:00
|
|
|
mod 'xinetd',
|
|
|
|
:git => 'https://github.com/puppetlabs/puppetlabs-xinetd',
|
2019-05-30 06:13:45 +00:00
|
|
|
:ref => 'v3.3.0'
|
2016-04-01 23:49:54 +00:00
|
|
|
|
|
|
|
mod 'memcached',
|
|
|
|
:git => 'https://github.com/saz/puppet-memcached',
|
2019-01-25 06:09:18 +00:00
|
|
|
:ref => 'v3.4.0'
|
2016-04-01 23:49:54 +00:00
|
|
|
|
|
|
|
mod 'python',
|
2018-07-31 21:23:58 +00:00
|
|
|
:git => 'https://github.com/voxpupuli/puppet-python',
|
2019-06-14 06:07:52 +00:00
|
|
|
:ref => 'v3.0.1'
|
2016-04-01 23:49:54 +00:00
|
|
|
|
|
|
|
mod 'dns',
|
|
|
|
:git => 'https://github.com/theforeman/puppet-dns',
|
2019-07-31 06:08:07 +00:00
|
|
|
:ref => '6.2.0'
|
2016-04-01 23:49:54 +00:00
|
|
|
|
2017-09-19 07:48:44 +00:00
|
|
|
mod 'archive',
|
|
|
|
:git => 'https://github.com/voxpupuli/puppet-archive',
|
2019-08-15 06:20:14 +00:00
|
|
|
:ref => 'v4.2.0'
|
2017-09-19 07:48:44 +00:00
|
|
|
|
2016-04-20 15:44:09 +00:00
|
|
|
mod 'corosync',
|
|
|
|
:git => 'https://github.com/voxpupuli/puppet-corosync',
|
2016-09-18 13:44:11 +00:00
|
|
|
:ref => 'v5.0.0'
|
2016-04-20 15:44:09 +00:00
|
|
|
|
2017-10-30 02:09:25 +00:00
|
|
|
mod 'ssh_keygen',
|
|
|
|
:git => 'https://github.com/voxpupuli/puppet-ssh_keygen',
|
|
|
|
:ref => 'v2.0.1'
|
2018-07-25 06:04:37 +00:00
|
|
|
|