OpenStack Cinder Puppet Module
Go to file
Sam Morrison 9055ae436a Add manage_package to RBD backend
Ability to not manage the ceph-common package by setting
this to false (Default: true)

Change-Id: I1f51d9ed3f4862f2c0e357cb86e7469333c2c208
2024-05-31 01:10:25 +00:00
doc Update openstackdocstheme to the latest version 2021-09-29 16:06:50 +08:00
examples Convert all class usage to relative names 2019-12-08 23:02:56 +01:00
lib/puppet cinder_type: Fix regex for properties to accept short value 2023-12-25 12:58:37 +09:00
manifests Add manage_package to RBD backend 2024-05-31 01:10:25 +00:00
releasenotes Add manage_package to RBD backend 2024-05-31 01:10:25 +00:00
spec Add manage_package to RBD backend 2024-05-31 01:10:25 +00:00
types rbd: More strictly validate rbd_ceph_conf 2024-03-29 09:03:47 +09:00
.gitignore Dissuade .gitignore references to personal tools 2018-10-08 11:39:23 +08:00
.gitreview OpenDev Migration Patch 2019-04-19 19:39:41 +00:00
.pdkignore Exclude release note files 2023-08-11 17:48:45 +09:00
.zuul.yaml Remove TripleO job 2023-03-13 11:14:10 +09:00
CHANGELOG.md Remove Dell EMC PS Series Driver aka Eqlx 2020-03-30 12:14:19 -05:00
CONTRIBUTING.rst [ussuri][goal] Add CONTRIBUTING.rst 2020-05-10 22:32:59 +02:00
Gemfile Use openstack_spec_helper from zuul checkout 2020-08-30 22:54:05 +02:00
LICENSE Update LICENSE 2018-04-06 20:14:09 +08:00
README.md Add Puppet Litmus 2020-08-31 21:13:59 +02:00
Rakefile Use puppet-openstack_spec_helper for Rakefile & spec_helper_acceptance 2016-01-18 09:11:14 -05:00
bindep.txt Add Puppet package to bindep, for module build 2017-10-27 13:11:29 -07:00
metadata.json Prepare 2024.1 release 2024-04-15 22:23:37 +09:00
setup.cfg Add information technology in the setup.cfg 2021-10-01 06:54:49 +08:00
setup.py setuptools: Disable auto discovery 2022-03-29 10:37:43 +02:00
tox.ini Stop configuring install_command in tox. 2021-09-29 09:02:57 +00:00

README.md

Team and repository tags

Team and repository tags

cinder

Table of Contents

  1. Overview - What is the cinder module?
  2. Module Description - What does the module do?
  3. Setup - The basics of getting started with cinder
  4. Implementation - An under-the-hood peek at what the module is doing
  5. Limitations - OS compatibility, etc.
  6. Development - Guide for contributing to the module
  7. Contributors - Those with commits
  8. Release Notes - Release notes for the project
  9. Repository - The project source code repository

Overview

The cinder 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 as part of the core software. The module its self is used to flexibly configure and manage the block storage service for OpenStack.

Module Description

The cinder module is a thorough attempt to make Puppet capable of managing the entirety of cinder. This includes manifests to provision such things as keystone endpoints, RPC configurations specific to cinder, and database connections. Types are shipped as part of the cinder module to assist in manipulation of configuration files.

This module is tested in combination with other modules needed to build and leverage an entire OpenStack software stack.

Setup

What the cinder module affects

  • Cinder, the block storage service for OpenStack.

Installing cinder

puppet module install openstack/cinder

Beginning with cinder

To utilize the cinder 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.

Define a cinder control node

class { 'cinder':
  database_connection   => 'mysql://cinder:secret_block_password@openstack-controller.example.com/cinder',
  default_transport_url => 'rabbit://cinder:secret_password@openstack-controller.example.com:5672',
}

class { 'cinder::api':
  keystone_password       => $keystone_password,
  keystone_user           => $keystone_user,
  keystone_auth_uri       => $keystone_auth_uri,
  service_port            => $keystone_service_port,
  package_ensure          => $cinder_api_package_ensure,
  bind_host               => $cinder_bind_host,
  enabled                 => $cinder_api_enabled,
}

class { 'cinder::scheduler': }

Define a cinder storage node

class { 'cinder':
  database_connection   => 'mysql://cinder:secret_block_password@openstack-controller.example.com/cinder',
  default_transport_url => 'rabbit://cinder:secret_password@openstack-controller.example.com:5672',
}

class { 'cinder::volume': }

cinder::backend::iscsi {
  'iscsi_example':
    target_ip_address => '10.0.0.2',
}

**Define a cinder storage node with multiple backends **

class { 'cinder':
  database_connection   => 'mysql://cinder:secret_block_password@openstack-controller.example.com/cinder',
  default_transport_url => 'rabbit://cinder:secret_password@openstack-controller.example.com:5672',
}

class { 'cinder::volume': }

cinder::backend::iscsi {'iscsi1':
  target_ip_address => '10.0.0.2',
}

cinder::backend::iscsi {'iscsi2':
  target_ip_address => '10.0.0.3',
}

cinder::backend::iscsi {'iscsi3':
  target_ip_address   => '10.0.0.4',
  volume_backend_name => 'iscsi',
}

cinder::backend::iscsi {'iscsi4':
  target_ip_address   => '10.0.0.5',
  volume_backend_name => 'iscsi',
}

cinder::backend::rbd {'rbd-images':
  rbd_pool => 'images',
  rbd_user => 'images',
}

cinder_type {'iscsi':
  ensure     => present,
  properties => ['volume_backend_name=iscsi,iscsi1,iscsi2'],
}

cinder_type {'rbd-images':
  ensure     => present,
  properties => ['volume_backend_name=rbd-images'],
}

class { 'cinder::backends':
  enabled_backends => ['iscsi1', 'iscsi2', 'rbd-images']
}

Note: that the name passed to any backend resource must be unique across all backends otherwise a duplicate resource will be defined.

** Using cinder_type **

Cinder allows for the usage of type to set extended information that can be used for various reasons. We have resource provider for cinder_type and if you want create some cinder type, you should set ensure to absent. Properties field is optional and should be an array. All items of array should match pattern key=value1[,value2 ...]. In case when you want to delete some type - set ensure to absent.

Implementation

cinder

cinder is a combination of Puppet manifest and ruby code to delivery configuration and extra functionality through types and providers.

Types

cinder_config

The cinder_config provider is a children of the ini_setting provider. It allows one to write an entry in the /etc/cinder/cinder.conf file.

cinder_config { 'DEFAULT/api_paste_config' :
  value => '/etc/cinder/api-paste.ini',
}

This will write api_paste_config=/etc/cinder/api-paste.ini in the [DEFAULT] section.

name

Section/setting name to manage from cinder.conf

value

The value of the setting to be defined.

secret

Whether to hide the value from Puppet logs. Defaults to false.

ensure_absent_val

If value is equal to ensure_absent_val then the resource will behave as if ensure => absent was specified. Defaults to <SERVICE DEFAULT>

Limitations

  • Setup of storage nodes is limited to Linux and LVM, i.e. Puppet won't configure a Nexenta appliance but nova can be configured to use the Nexenta driver with Class['cinder::volume::nexenta'].

Development

Developer documentation for the entire puppet-openstack project.

Contributors

Release Notes

Repository