Alex Schultz 3b878cdb0f Add missing openstacklib and keystone dependencies
The ceph module includes a class from openstacklib and the keystone
providers for keystone integration. This change adds in this dependency
to the metadata.json to capture this requirement. These are only
required for keystone integration if you plan on using the ceph class to
set those up.

Change-Id: Iab834f775aad54b0545e791337ea7b76a5daee4b
2017-09-25 08:25:49 -06:00
2017-09-22 03:23:45 +00:00
2017-09-04 14:19:58 +00:00
2016-07-07 16:27:14 -04:00
2015-11-05 17:15:13 -05:00
2017-05-18 18:06:56 +02:00
2017-05-18 18:06:56 +02:00
2013-10-20 22:45:54 -07:00
2016-07-07 16:27:14 -04:00
2016-05-06 17:54:13 -04:00
2017-06-12 15:48:06 +08:00

Team and repository tags

Team and repository tags

ceph

Table of Contents

  1. Overview - What is the ceph module?
  2. Module Description - What does the module do?
  3. Setup - The basics of getting started with ceph
  4. Implementation - An under-the-hood peek at what the module is doing
  5. Limitations - OS compatibility, etc.
  6. Use Cases - Examples of how to use this module
  7. Development - Guide for contributing to the module
  8. Beaker Integration Tests - Apply the module and test restults
  9. Contributors - Those with commits
  10. Release Notes - Notes on the most recent updates to the module

Overview

The ceph module is intended to leverage all Ceph has to offer and allow for a wide range of use case. Although hosted on the OpenStack infrastructure, it does not require to sign a CLA nor is it restricted to OpenStack users. It benefits from a structured development process that helps federate the development effort. Each feature is tested with integration tests involving virtual machines to show that it performs as expected when used with a realistic scenario.

Module Description

The ceph module deploys a Ceph cluster ( MON, OSD ), the Cephfs file system and the RadosGW object store. It provides integration with various environments ( OpenStack ... ) and components to be used by third party puppet modules that depend on a Ceph cluster.

Setup

Implementation

A blueprint contains an inventory of what is desirable. It was decided to start from scratch and implement one module at a time.

Limitations

We follow the OS compatibility of Ceph. With the release of infernalis this is currently:

  • CentOS 7 or later
  • Debian Jessie 8.x or later
  • Ubuntu Trusty 14.04 or later
  • Fedora 22 or later

Use Cases

Development

git clone https://github.com/openstack/puppet-ceph.git
cd puppet-ceph
sudo gem install bundler
bundle install

The developer documentation of the puppet-openstack project is the reference:

Mailing lists:

IRC channels:

  • irc.freenode.net#puppet-openstack
  • irc.oftc.net#ceph-devel

Beaker Integration Tests

Relies on rspec-beaker and tests are in spec/acceptance. It also requires Vagrant and Virtualbox .

bundle install
bundle exec rspec spec/acceptance

The BEAKER_set environment variable contains the resource set of linux distribution configurations for which integration tests are going to be run. Available values are

  • two-centos-70-x64
  • centos-70-x64
  • two-ubuntu-server-1404-x64
  • ubuntu-server-1404-x64

The default is

BEAKER_set=two-ubuntu-server-1404-x64 \
bundle exec rspec spec/acceptance

Contributors

Release Notes

Description
Ceph Puppet Module
Readme 10 MiB
Languages
Ruby 55.4%
Puppet 40%
Python 3.7%
Pascal 0.9%