b97a053485
Compute nodes don't need a public IP and therefore it isn't possible to get a list of public networks on such hosts. This commit fixes the logic so it returns an empty list, instead of erroring on 'none' string. Change-Id: I3cab92120b41794967c9affcbdeafb386c2ec9e0 Closes-Bug: #1520553 |
||
---|---|---|
debian | ||
deployment | ||
files | ||
logs | ||
specs | ||
tests | ||
utils | ||
.gitignore | ||
.gitreview | ||
CHANGELOG | ||
Gemfile | ||
LICENSE | ||
MAINTAINERS | ||
Rakefile | ||
README.md |
fuel-library
Table of Contents
- Overview - What is the fuel-library?
- Structure - What is in the fuel-library?
- Granular Deployment - What is the granular deployment for Fuel?
- Upstream Modules - How to work with librarian.
- Testing - How to run fuel-library tests.
- Development
- Core Reviers
- Contributors
Overview
The fuel-library is collection of Puppet modules and related code used by Fuel to deploy OpenStack environments.
Structure
Basic Repository Layout
fuel-library
├── CHANGELOG
├── LICENSE
├── README.md
├── debian
├── deployment
├── files
├── specs
├── tests
└── utils
root
The root level contains important repository documentation and license information.
debian/
This folder contains the required information to create fuel-library debian packages.
deployment/
This folder contains the fuel-library Puppet code, the Puppetfile for upstream modules, and scripts to manage modules with librarian-puppet-simple.
files/
This folder contains scripts and configuration files that are used when creating the packages for fuel-library.
specs/
This folder contains our rpm spec file for fuel-library rpm packages.
tests/
This folder contains our testing scripts for the fuel-library.
utils/
This folder contains scripts that are useful when doing development on fuel-library
Granular Deployment
TODO.
Upstream Modules
In order to be able to pull in upstream modules for use by the fuel-library, the deployment folder contains a Puppetfile for use with librarian-puppet-simple. Upstream modules should be used whenever possible. For additional details on the process for working with upstream modules, please read the Fuel library for Puppet manifests of the Fuel wiki.
Testing
Testing is important for the fuel-library to ensure changes do what they are supposed to do, regressions are not introduced and all code is of the highest quality. The fuel-library leverages existing Puppet module rspec tests, bats tests for bash scripts and noop tests for testing the module deployment tasks in fuel-library.
Puppet module tests
TODO.
Bats: Bash Automated Testing System
TODO.
fuel-library noop
TODO.