fce2e2a764
After backup-reinstall-restore Fuel uses bootstrap with wrong ssh keys. dockerctl backup procedure does not save the bootstrap's root filesystem, which holds the list of authorized keys that should be matching the private key located in /root/.ssh on the master. It would result in inaccessible nodes from a new master installation (which has bootstrap images regenerated with a new key, not matching the original one, restored from the backup). This patch updates authorized_keys inside squashfsed bootstrap images, so it will be retained during backup-reinstall-restore procedure, if user has not requested a full backup. Full backups already contain a full copy of /var/www/nailgun, so no changes are needed. User should carefully restore from non-full backups - only active bootstrap will have its ssh keys updated. To propagate ssh keys to already running nodes, you can use something like: mco rpc --agent execute_shell_command --action execute --arg cmd="echo '$(cat /root/.ssh/id_rsa.pub)' >> /root/.ssh/authorized_keys" -v Change-Id: I3945200d02b29ed10e60900f7d03ed30970159a3 Closes-Bug: #1536198 DocImpact |
||
---|---|---|
debian | ||
deployment | ||
doc/noop-guide | ||
files | ||
logs | ||
specs | ||
tests | ||
utils | ||
.gitignore | ||
.gitreview | ||
CHANGELOG | ||
Gemfile | ||
LICENSE | ||
MAINTAINERS | ||
README.md | ||
Rakefile | ||
doc-test.conf | ||
test-requirements.txt | ||
tox.ini |
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.
- Building docs - How to build docs.
- 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
├── MAINTAINERS
├── debian
├── deployment
├── doc
├── files
├── specs
├── tests
└── utils
root
The root level contains important repository documentation and license information.
MAINTAINERS
This is repository level MAINTAINERS file. One submitting a patch should contact the apropriate maintainer or invite her or him for the code review. Note, core reviewers are not the maintainers. Normally, cores do reviews after maintainers.
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.
doc/
This folder contains RST docs. Currently there is only docs for Noop testing framework.
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
The top-scope puppet manifests (sometimes also refered as the composition layer) represent the known deploy paths (aka supported deployment scenarios) for the task-based deployment.
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.
Building docs
You can use tox to prepare virtual environment and build all RST based guides:
tox -e docs
You can also build a specific guide. For example, to build Noop Tests How-to Guide, use the following command:
tox -e build -- noop-guide
You can find the root of the generated HTML documentation at:
./doc/noop-guide/build/html/index.html
You can also run docs tests with tox
.
If you like to run individual tests, run:
tox -e checkniceness
- to run the niceness teststox -e checksyntax
- to run syntax checks
tox will use the openstack-doc-tools package for execution of these tests.
Puppet module tests
Puppet rspec tests should be provided for an every module's directory included.
All of the discovered tests will be automatically executed by the
rake spec
command issued from the repository root path.
Bats: Bash Automated Testing System
Shell scripts residing in the ./files
directories should be
covered by the BATS test cases.
These should be put under the ./tests/bats
path as well.
Here is an example bats tests
written for the UMM feature.
See also the bats how-to.
fuel-library noop
The Noop testing framework is used for testing of the known deploy paths with existing modular tasks. For details, see the README