Team and repository tags
Table of Contents
- Overview - What is the magnum module?
- Module Description - What does the module do?
- Setup - The basics of getting started with magnum
- Implementation - An under-the-hood peek at what the module is doing
- Limitations - OS compatibility, etc.
- Development - Guide for contributing to the module
- Contributors - Those with commits
- Release Notes - Release notes for the project
- Repository - The project source code repository
The magnum 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 itself is used to flexibly configure and manage the container service for OpenStack.
The magnum module is a thorough attempt to make Puppet capable of managing the entirety of magnum. This includes manifests to provision region specific endpoint and database connections. Types are shipped as part of the magnum module to assist in manipulation of configuration files.
What the magnum module affects
- Magnum, the container service for OpenStack.
magnum is not currently in Puppet Forge, but is anticipated to be added soon. Once that happens, you'll be able to install magnum with:
puppet module install openstack/magnum
Beginning with magnum
To utilize the magnum module's functionality you will need to declare multiple resources. This is not an exhaustive list of all the components needed, we recommend you consult and understand the core openstack documentation.
magnum is a combination of Puppet manifest and ruby code to delivery configuration and extra functionality through types and providers.
- All the magnum types use the CLI tools and so need to be run on the magnum node.
Developer documentation for the entire puppet-openstack project.