d14693bde4
bifrost is composing network ids with ipv4+mac, while sys_interfaces is just a dict with mac:nic values. Get rid of that ipv4 prefix when searching for the right interface to create the bridge. We will be trying first to retrieve the original id, then get rid of ipv4- as a fallback. Change-Id: I78ac1e6b735cbc2cc120c92f6c9bf1492924f5e4
infracloud
Table of Contents
- Overview - What is the infracloud module?
- Module Description - What does the module do?
- Setup - The basics of getting started with infracloud
- 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
Overview
The infracloud module is a part of OpenStack-infra, an effort by the OpenStack infrastructure team to provide continuous integration testing and code review for OpenStack-infra projects.
Module Description
The infracloud module is a thorough attempt to make Puppet capable of managing the entirety of infracloud. This includes manifests to provision the expected features of this module. Types are shipped as part of the infracloud module to assist in manipulation of configuration files.
Setup
Installing infracloud
infracloud is not currently in Puppet Forge, but is anticipated to be added soon. Once that happens, you'll be able to install infracloud with:
puppet module install openstack-infra/infracloud
Beginning with infracloud
To utilize the infracloud module's functionality please check the README.
Implementation
infracloud
infracloud is a combination of Puppet manifests to delivery configuration and extra functionality through types and providers.
Beaker-Rspec
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:
Development
Developer documentation for the entire puppet-infra project.