OpenStack Glance Puppet Module
Go to file
Emilien Macchi 13281189b2 Add other-requirements.txt for bindep
Bindep is a binary automation tool used in openstack-infra.  With it,
projects can better control the default packages installed into the
OS. Because we are using puppet, we actually don't want any packages
installed by default as to better test our manifests.

Change-Id: I3cb870959a8e9b009fffbc65a544aef6ed2c3b68
Co-Authored-By: Paul Belanger <pabelanger@redhat.com>
2016-05-19 22:09:16 +00:00
examples Add glance multi/single store declaration examples 2016-03-08 17:37:12 +00:00
ext update passwords from test script 2012-10-31 16:03:43 -07:00
lib/puppet Fix image list in glance_image provider 2016-04-08 19:27:00 +00:00
manifests Deprecate verbose option in logging 2016-05-18 01:12:46 -03:00
releasenotes Deprecate verbose option in logging 2016-05-18 01:12:46 -03:00
spec Deprecate verbose option in logging 2016-05-18 01:12:46 -03:00
tests Deprecate verbose option in logging 2016-05-18 01:12:46 -03:00
.gitignore Add basic structure for ReNo 2016-03-14 08:28:13 -04:00
.gitreview Update .gitreview file for project rename 2015-06-12 23:12:30 +00:00
CHANGELOG.md Release 8.0.0 2016-03-23 16:07:06 -04:00
Gemfile Gemfile: rely on puppet-openstack_spec_helper for dependencies 2016-03-29 21:36:10 -04:00
LICENSE Synchronize LICENSE file with OpenStack projects 2015-04-20 09:05:59 -04:00
README.md Deprecate verbose option in logging 2016-05-18 01:12:46 -03:00
Rakefile Use puppet-openstack_spec_helper for Rakefile & spec_helper_acceptance 2016-01-18 09:11:17 -05:00
metadata.json Use oslo module for messaging (rabbit) configuration 2016-04-13 13:29:23 +03:00
other-requirements.txt Add other-requirements.txt for bindep 2016-05-19 22:09:16 +00:00
setup.cfg Add basic structure for ReNo 2016-03-14 08:28:13 -04:00
setup.py Add basic structure for ReNo 2016-03-14 08:28:13 -04:00
test-requirements.txt Add basic structure for ReNo 2016-03-14 08:28:13 -04:00
tox.ini Add basic structure for ReNo 2016-03-14 08:28:13 -04:00

README.md

glance

7.0.0 - 2015.2 - Liberty

Table of Contents

  1. Overview - What is the glance module?
  2. Module Description - What does the module do?
  3. Setup - The basics of getting started with glance
  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

Overview

The glance 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 image service for OpenStack.

Module Description

The glance module is a thorough attempt to make Puppet capable of managing the entirety of glance. This includes manifests to provision such things as keystone endpoints, RPC configurations specific to glance, and database connections. Types are shipped as part of the glance 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 glance module affects

  • Glance, the image service for OpenStack.

Installing glance

puppet module install openstack/glance

Beginning with glance

To utilize the glance 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 glance node

class { 'glance::api':
  keystone_tenant     => 'services',
  keystone_user       => 'glance',
  keystone_password   => '12345',
  database_connection => 'mysql://glance:12345@127.0.0.1/glance',
}

class { 'glance::registry':
  keystone_tenant     => 'services',
  keystone_user       => 'glance',
  keystone_password   => '12345',
  database_connection => 'mysql://glance:12345@127.0.0.1/glance',
}

class { 'glance::backend::file': }

Setup postgres node glance

class { 'glance::db::postgresql':
  password => '12345',
}

Setup mysql node for glance

class { 'glance::db::mysql':
  password      => '12345',
  allowed_hosts => '%',
}

Setup up keystone endpoints for glance on keystone node

class { 'glance::keystone::auth':
  password         => '12345'
  email            => 'glance@example.com',
  public_address   => '172.17.0.3',
  admin_address    => '172.17.0.3',
  internal_address => '172.17.1.3',
  region           => 'example-west-1',
}

Setup up notifications for multiple RabbitMQ nodes

class { 'glance::notify::rabbitmq':
  rabbit_password               => 'pass',
  rabbit_userid                 => 'guest',
  rabbit_hosts                  => [
    'localhost:5672', 'remotehost:5672'
  ],
  rabbit_use_ssl                => false,
}

Types

glance_api_config

The glance_api_config provider is a children of the ini_setting provider. It allows one to write an entry in the /etc/glance/glance-api.conf file.

glance_api_config { 'DEFAULT/image_cache_dir' :
  value => /var/lib/glance/image-cache,
}

This will write image_cache_dir=/var/lib/glance/image-cache in the [DEFAULT] section.

name

Section/setting name to manage from glance-api.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>

glance_registry_config

The glance_registry_config provider is a children of the ini_setting provider. It allows one to write an entry in the /etc/glance/glance-registry.conf file.

glance_registry_config { 'DEFAULT/workers' :
  value => 1,
}

This will write workers=1 in the [DEFAULT] section.

name

Section/setting name to manage from glance-registry.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>

glance_cache_config

The glance_cache_config provider is a children of the ini_setting provider. It allows one to write an entry in the /etc/glance/glance-cache.conf file.

glance_cache_config { 'DEFAULT/image_cache_stall_time' :
  value => 86400,
}

This will write image_cache_stall_time=86400 in the [DEFAULT] section.

name

Section/setting name to manage from glance-cache.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>

Implementation

glance

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

Limitations

  • Only supports configuring the file, swift and rbd storage backends.

Beaker-Rspec

This module has beaker-rspec tests

To run the tests on the default vagrant node:

To run:

bundle install
bundle exec rspec spec/acceptance

For more information on writing and running beaker-rspec tests visit the documentation:

Development

Developer documentation for the entire puppet-openstack project.

Contributors