Prepare Train M2
Update the version metadata for Train milestone 2 Change-Id: I25f123fe420a44d9da1777a5983e955f8f0e252e
|1 month ago|
|doc||1 year ago|
|examples||7 months ago|
|lib/puppet||2 years ago|
|manifests||2 months ago|
|releasenotes||2 months ago|
|spec||1 month ago|
|.gitignore||9 months ago|
|.gitreview||2 months ago|
|.zuul.yaml||10 months ago|
|Gemfile||2 months ago|
|LICENSE||1 year ago|
|README.md||2 months ago|
|Rakefile||2 years ago|
|bindep.txt||1 year ago|
|metadata.json||1 month ago|
|setup.cfg||7 months ago|
|setup.py||2 years ago|
|tox.ini||2 months ago|
The freezer module is a part of OpenStack, an effort by the OpenStack infrastructure team to provide continuous integration testing and code review for OpenStack and OpenStack community projects not part of the core software. The module its self is used to flexibly configure and manage the distributed backup restore and disaster recovery as a service platform for OpenStack.
The freezer module is a thorough attempt to make Puppet capable of managing the entirety of freezer. This includes manifests to provision region specific endpoint and database connections. Types are shipped as part of the freezer module to assist in manipulation of configuration files.
What the freezer module affects
freezer is not currently in Puppet Forge, but is anticipated to be added soon. Once that happens, you'll be able to install freezer with: puppet module install openstack/freezer
To utilize the freezer module’s functionality you will need to declare multiple resources.
freezer is a combination of Puppet manifest and ruby code to delivery configuration and extra functionality through types and providers.
This module has beaker-rspec tests
To run the tests on the default vagrant node:
bundle install bundle exec rake acceptance
For more information on writing and running beaker-rspec tests visit the documentation:
Developer documentation for the entire puppet-openstack project.