Version information
This version is compatible with:
- Puppet Enterprise 2023.2.x, 2023.1.x, 2023.0.x, 2021.7.x, 2021.6.x, 2021.5.x, 2021.4.x, 2021.3.x, 2021.2.x, 2021.1.x, 2021.0.x
- Puppet >= 7.0.0 < 8.0.0
- , , ,
Start using this module
Add this module to your Puppetfile:
mod 'openstack-openstacklib', '25.0.0'
Learn more about managing modules with a PuppetfileDocumentation
Team and repository tags
openstacklib
Table of Contents
- Overview - What is the openstacklib module?
- Module Description - What does the module do?
- Setup - The basics of getting started with openstacklib
- Usage - The usage of the openstacklib module
- Implementation - An under-the-hood peek at what the module is doing
- Limitations - OS compatibility, etc.
- Development - Guide for contributing to the module
- Contributors - Those with commits
- Release Notes - Release notes for the project
- Repository - The project source code repository
Overview
The openstacklib 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 not part of the core software. The module itself is used to expose common functionality between Openstack modules as a library that can be utilized to avoid code duplication.
Module Description
The openstacklib module is a library module for other Openstack modules to utilize. A thorough description will be added later.
This module is tested in combination with other modules needed to build and leverage an entire Openstack software stack.
Setup
Installing openstacklib
puppet module install openstack/openstacklib
Usage
Classes and Defined Types
Defined type: openstacklib::db::mysql
The db::mysql resource is a library resource that can be used by nova, cinder, ceilometer, etc., to create a mysql database with configurable privileges for a user connecting from defined hosts.
Typically this resource will be declared with a notify parameter to configure the sync command to execute when the database resource is changed.
For example, in heat::db::mysql you might declare:
::openstacklib::db::mysql { 'heat':
password_hash => mysql::password($password),
dbname => $dbname,
user => $user,
host => $host,
charset => $charset,
collate => $collate,
allowed_hosts => $allowed_hosts,
notify => Exec['heat-dbsync'],
}
Some modules should ensure that the database is created before the service is set up. For example, in keystone::db::mysql you would have:
::openstacklib::db::mysql { 'keystone':
password_hash => mysql::password($password),
dbname => $dbname,
user => $user,
host => $host,
charset => $charset,
collate => $collate,
allowed_hosts => $allowed_hosts,
notify => Exec['keystone-manage db_sync'],
before => Service['keystone'],
}
Parameters for openstacklib::db::mysql:
#####password_hash
Password hash to use for the database user for this service;
string; required
#####dbname
The name of the database
string; optional; default to the $title of the resource, i.e. 'nova'
#####user
The database user to create;
string; optional; default to the $title of the resource, i.e. 'nova'
#####host
The IP address or hostname of the user in mysql_grant;
string; optional; default to '127.0.0.1'
#####charset
The charset to use for the database;
string; optional; default to 'utf8'
#####collate
The collate to use for the database;
string; optional; default to 'utf8_general_ci'
#####allowed_hosts
Additional hosts that are allowed to access this database;
array or string; optional; default to undef
#####privileges
Privileges given to the database user;
string or array of strings; optional; default to 'ALL'
Defined type: openstacklib::db::postgresql
The db::postgresql resource is a library resource that can be used by nova, cinder, ceilometer, etc., to create a postgresql database and a user with configurable privileges.
Typically this resource will be declared with a notify parameter to configure the sync command to execute when the database resource is changed.
For example, in heat::db::postgresql you might declare:
::openstacklib::db::postgresql { $dbname:
password_hash => postgresql_password($user, $password),
dbname => $dbname,
user => $user,
notify => Exec['heat-dbsync'],
}
Some modules should ensure that the database is created before the service is set up. For example, in keystone::db::postgresql you would have:
::openstacklib::db::postgresql { $dbname:
password_hash => postgresql_password($user, $password),
dbname => $dbname,
user => $user,
notify => Exec['keystone-manage db_sync'],
before => Service['keystone'],
}
Parameters for openstacklib::db::postgresql:
#####password_hash
Password hash to use for the database user for this service;
string; required
#####dbname
The name of the database
string; optional; default to the $title of the resource, i.e. 'nova'
#####user
The database user to create;
string; optional; default to the $title of the resource, i.e. 'nova'
#####encoding
The encoding use for the database;
string; optional; default to undef
#####privileges
Privileges given to the database user;
string or array of strings; optional; default to 'ALL'
Defined type: openstacklib::service_validation
The service_validation resource is a library resource that can be used by nova, cinder, ceilometer, etc., to validate that a resource is actually up and running.
For example, in nova::api you might declare:
::openstacklib::service_validation { 'nova-api':
command => 'nova list',
}
This defined resource creates an exec-anchor pair where the anchor depends upon the successful exec run.
Parameters for openstacklib::service_validation:
#####command
Command to run for validating the service;
string; required
#####service_name
The name of the service to validate;
string; optional; default to the $title of the resource, i.e. 'nova-api'
#####path
The path of the command to validate the service;
string; optional; default to '/usr/bin:/bin:/usr/sbin:/sbin'
#####provider
The provider to use for the exec command;
string; optional; default to 'shell'
#####tries
Number of times to retry validation;
string; optional; default to '10'
#####try_sleep
Number of seconds between validation attempts;
string; optional; default to '2'
Defined provider for openstack_config: ini_setting
It provides an interface to any INI configuration file as they are used in Openstack modules.
You use it like this:
Puppet::Type.type(:<module>_config).provide(
:openstackconfig,
:parent => Puppet::Type.type(:openstack_config).provider(:ini_setting)
) do
It has the standard features of the upstream puppetlabs' inifile
module as it's a direct children of it. Furthermore it can transform
a value with some function of you're choice, enabling you to get value
that get filled at run-time like an uuid
.
For an example of how that's working you can have a look at this review
Defined provider for openstack_config: ruby
This one has the same basic features as the ini_setting one but the ability to transformation the value. It offers another feature, though. It can parse array. What it enables one to do is to parse this correctly:
[DEFAULT]
conf1 = value1
conf1 = value2
On the opposite side if you put that:
module_config { 'DEFAULT/conf1' : value => ['value1', 'value2'] }
in your manifest, it will properly be written as the example above.
To use this provider you use this:
Puppet::Type.type(:<module>_config).provide(
:openstackconfig,
:parent => Puppet::Type.type(:openstack_config).provider(:ruby)
) do
and define you type with :array_matching => :all
. An example of
such provider is nova_config
. Have a look for inspiration.
Implementation
openstacklib
openstacklib is a combination of Puppet manifest and ruby code to delivery configuration and extra functionality through types and providers.
Limitations
The python-migrate system package for RHEL 6 and below is out of date and may fail to correctly migrate postgresql databases. While this module does not handle database migrations, it is common to set up refresh relationships between openstacklib::db::postgresql resource and the database sync exec resource. Relying on this behavior may cause errors.
Development
Developer documentation for the entire puppet-openstack project.
Contributors
Release Notes
Repository
8.0.0 and beyond
From 8.0.0 release and beyond, release notes are published on docs.openstack.org.
##2015-11-24 - 7.0.0 ###Summary
This is a backwards-compatible major release for OpenStack Liberty.
####Features
- fallback to default rcfile
- prepare $::os_package_type
- add a proxy inifile provider
- allow the use of an ensure_absent_val param
- create is_service_default function
- create os_service_default fact
- allow to path custom fragment to vhost
- pass necessary options to Apache when using WSGI
####Bugfixes
- fix fact for puppet facter 2.0.1+
####Maintenance
- initial msync run for all Puppet OpenStack modules
- enable acceptance tests for openstack_config
- remove class_parameter_defaults puppet-lint check
##2015-10-10 - 6.1.0 ###Summary
This is a maintenance release in the Kilo series.
####Maintenance
- acceptance: checkout stable/kilo puppet modules
##2015-07-08 - 6.0.0 ###Summary
This is a backwards-incompatible major release for OpenStack Kilo.
####Backwards-incompatible changes
- MySQL: change default MySQL collate to utf8_general_ci
####Features
- Puppet 4.x support
- Add db::postgresql to openstacklib
- Implement openstacklib::wsgi::apache
- Move openstackclient parent provider to openstacklib
- Keystone V3 API support
- Restructures authentication for resource providers
####Bugfixes
- Properly handle policy values containing spaces
####Maintenance
- Bump mysql version to 3.x
- Acceptance tests with Beaker
##2015-06-17 - 5.1.0 ###Summary
This is a feature and bugfix release in the Juno series.
####Features
- Adding augeas insertion check
####Bugfixes
- MySQL: change default MySQL collate to utf8_general_ci
####Maintenance
- Update .gitreview file for project rename
- spec: pin rspec-puppet to 1.0.1
##2014-11-25 - 5.0.0 ###Summary
Initial release for Juno.
Dependencies
- puppetlabs/apache (>=5.0.0 <13.0.0)
- puppetlabs/inifile (>=2.0.0 <7.0.0)
- puppetlabs/mysql (>=6.0.0 <17.0.0)
- puppetlabs/stdlib (>=5.0.0 <10.0.0)
- puppet/rabbitmq (>=2.0.2 <14.0.0)
- puppetlabs/postgresql (>=6.4.0 <11.0.0)
Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.