1.0.0 - 2014.2.0 - Juno
- Overview - What is the manila module?
- Module Description - What does the module do?
- Setup - The basics of getting started with manila
- Implementation - An under-the-hood peek at what the module is doing
- Development - Guide for contributing to the module
- Contributors - Those with commits
- Release Notes - Notes on the most recent updates to the module
The manila module is part of Stackforge, 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 file system service for OpenStack.
The manila module is a thorough attempt to make Puppet capable of managing the entirety of manila. This includes manifests to provision such things as keystone endpoints, RPC configurations specific to manila, and database connections.
This module is tested in combination with other modules needed to build and leverage an entire OpenStack software stack. These modules can be found, all pulled together in the openstack module.
What the manila module affects
- manila, the file system service for OpenStack.
manila is not currently in Puppet Forge, but is anticipated to be added soon. Once that happens, you'll be able to install manila with:
puppet module install puppetlabs/manila
To utilize the manila module's functionality you will need to declare multiple resources. [TODO: add example]
manila is a combination of Puppet manifests and ruby code to delivery configuration and extra functionality through types and providers.
Developer documentation for the entire puppet-openstack project.
1.0.0
- Initial commit