Version information
This version is compatible with:
- Puppet Enterprise 3.x
- Puppet 3.x
- , , ,
Start using this module
Add this module to your Puppetfile:
mod 'stackforge-nova', '5.2.0'
Learn more about managing modules with a PuppetfileDocumentation
nova
5.2.0 - 2014.2 - Juno
Table of Contents
- Overview - What is the nova module?
- Module Description - What does the module do?
- Setup - The basics of getting started with nova
- 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 - Notes on the most recent updates to the module
Overview
The nova module is a part of Stackforge, 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 its self is used to flexibly configure and manage the compute service for Openstack.
Module Description
The nova module is a thorough attempt to make Puppet capable of managing the entirety of nova. This includes manifests to provision such things as keystone endpoints, RPC configurations specific to nova, and database connections. Types are shipped as part of the nova 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. These modules can be found, all pulled together in the openstack module.
Setup
What the nova module affects:
- nova, the compute service for Openstack.
Installing nova
example% puppet module install puppetlabs/nova
Beginning with nova
To utilize the nova module's functionality you will need to declare multiple resources. The following is a modified excerpt from the openstack module. This is not an exhaustive list of all the components needed, we recommend you consult and understand the openstack module and the core openstack documentation.
class { 'nova':
database_connection => 'mysql://nova:a_big_secret@127.0.0.1/nova?charset=utf8',
rabbit_userid => 'nova',
rabbit_password => 'an_even_bigger_secret',
image_service => 'nova.image.glance.GlanceImageService',
glance_api_servers => 'localhost:9292',
verbose => false,
rabbit_host => '127.0.0.1',
}
class { 'nova::compute':
enabled => true,
vnc_enabled => true,
}
class { 'nova::compute::libvirt':
migration_support => true,
}
Implementation
nova
nova is a combination of Puppet manifest and ruby code to delivery configuration and extra functionality through types and providers.
Limitations
- Supports libvirt, xenserver and vmware compute drivers.
- Tested on EL and Debian derivatives.
Development
Developer documentation for the entire puppet-openstack project.
Contributors
Release Notes
5.2.0
- Remove dead providers
- Add an ability to manage use_stderr parameter
- Remove utf-8 characters
- Ensure /etc/nova exists before creating secret.xml
5.1.0
- move setting of novncproxy_base_url
- Added parameters for availability zones configuration
- crontab: ensure nova-common is installed before
- Correct docs on format for nova::policy data
- Allow libvirt secret key setting from param
- Fix behaviour of 'set-secret-value virsh' exec
- MySQL: change default MySQL collate to utf8_general_ci
- Pin puppetlabs-concat to 1.2.1 in fixtures
- Make group on /var/log/nova OS specific
- IPv6 support for migration check.
- Database: add slave_connection support
- Correct references to ::nova::rabbit_* variables
- Add optional network_api_class parameter to nova::network::neutron class
- Add Nova Aggregate support
- rpc_backend: simplify parameters
- supporting lxc cpu mode Fixing the default cpu_mode from None to none
- virsh returns a list of secret uuids, not keyring names
- Pin fixtures for stables branches
- Add serialproxy configuration
- Switch to TLSv1 as SSLv3 is considered insecure and is disabled by default
- Disable file injection when using RBD as compute ephemeral storage
- Add PCI Passthrough/SR-IOV support
- Add Ironic support into nova puppet modules
- spec: pin rspec-puppet to 1.0.1
- Correct section for cell_type nova.conf parameter
- crontab: ensure the script is run with shell
- Configure database parameters on the right nodes
5.0.0
- Stable Juno release
- Added tags to all nova packages
- Added parameter dhcp_domain to nova class
- Updated the [glance] and [neutron] section parameters for Juno
- Fixed potential duplicate declaration errors for sysctl::value in nova::network
- Fixed dependency cycle in nova::migration::libvirt
- Updated the libvirtd init script path for Debian
- Added parameters for nova service validation to nova::api
- Added nova::policy to control policy.json
- Fixed the rabbit_virtual_host default in nova::cells
- Bumped stdlib dependency to >=4.0.0
- Added force_raw_images parameter to nova::compute class
- Replaced usage of the keyword type with the string 'type' since type is a reserved keyword in puppet 3.7
- Added parameter ec2_workers to nova::api
- Fixed bug in usage of --vlan versus --vlan_start in nova_network provider
- Added parameter rabbit_ha_queues to nova class
- Added parameter pool to nova_floating type
- Added parameters to control whether to configure keystone users
- Added nova::cron::archive_deleted_rows class to create a crontab for archiving deleted database rows
- Changed the keystone_service to only be configured if the endpoint is to be configured
- Added parameter keystone_ec2_url to nova::api
- Added the ability to override the keystone service name in ceilometer::keystone::auth
- Removed dynamic scoping of File resources in nova class
- Add parameter workers to in nova::conductor and deprecate conductor_workers in nova::api
- Update nova quota parameters for Juno
- Migrated the ceilometer::db::mysql class to use openstacklib::db::mysql and deprecated the mysql_module parameter
- Removed deprecation notice for sectionless nova_config names
- Added parameter vnc_keymap in nova::compute
- Added parameter osapi_v3 to nova::api
4.2.0
- Added option to configure libvirt service name via class parameters
- Added support for multiple SSL APIs
- Added option to configure os_region_name in the nova config
- Corrected resource dependencies on the nova user
- Fixed os version fact comparison for RedHat-based operating systems for specifying service provider
- Fixed ssl parameter requirements when using kombu and rabbit
- Added class for extended logging options
4.1.0
- Added API v3 endpoint support.
- Added configuration of rbd keyring name.
- Added support for run Nova SSL endpoints.
- Updated RabbitMQ dependency.
- Updated mysql charset to UTF8.
- Pinned major gems.
4.0.0
- Stable Icehouse release.
- Added support for RHEL 7.
- Added support for metadata and conductor workers.
- Added support for vif_plugging parameters.
- Added support for puppetlabs-mysql 2.2 and greater.
- Added support for instance_usage_audit parameters.
- Added support to manage the nova uid/gid for NFS live migration..
- Added nova::config to handle additional custom options.
- Added support to disable installation of nova utilities.
- Added support for durable RabbitMQ queues.
- Added SSL support for RabbitMQ.
- Added support for nova-objectstore bind address.
- Updated support for notification parameters.
- Fixed packaging bugs.
- Fixed report_interval configuration.
- Fixed file location for nova compute rbd secret.
3.2.1
- Fixed consoleauth/spice resource duplication on Red Hat systems.
3.2.0
- Replace pip with native package manager for VMWare.
- Deprecated logdir parameter in favor of log_dir.
- Allows log_dir to be set to false in order to disable file logging.
- Enables libvirt at boot.
- Adds RBD backend support for VM image storage.
- Parameterizes libvirt cpu_mode and disk_cachemodes.
- Adds support for https auth endpoints.
- Adds ability to disable installation of nova utilities.
3.1.0
- Minor release for OpenStack Havana.
- Add libguestfs-tools package to nova utilities.
- Fixed vncproxy package naming for Ubuntu.
- Fixed libvirt configuration.
3.0.0
- Major release for OpenStack Havana.
- Removed api-paste.ini configuration.
- Adds support for live migrations with using the libvirt Nova driver.
- Fixed bug to ensure keystone endpoint is set before service is started.
- Fixed nova-spiceproxy support on Ubuntu.
- Added support for VMWareVCDriver.
2.2.0
- Added a check to install bridge-utils only if needed.
- Added syslog support.
- Added installation of pm-utils for VM power management support.
- Fixed cinder include dependency bug.
- Various bug and lint fixes.
2.1.0
- Added support for X-Forwarded-For HTTP Headers.
- Added html5 spice support.
- Added config drive support.
- Added RabbitMQ clustering support.
- Added memcached support.
- Added SQL idle timeout support.
- Fixed allowed_hosts/database connection bug.
- Pinned RabbitMQ and database module versions.
2.0.0
- Upstream is now part of stackforge.
- The ini_file type is now used by nova_config.
- Support for nova-conductor added.
- Networks can now be labeled by Class['nova::manage::network'].
- The Apache Qpid message broker is available as an RPC backend.
- Further compatibility fixes for RHEL and its derivatives.
- Postgres support added.
- Adjustments to help in supporting the still in development neutron module.
- Config changes can be hidden from Puppet logs.
- Move from deprecated rabbit_notifier to rpc_notifier.
- Various cleanups and bug fixes.
Types in this module release
Dependencies
- dprince/qpid (>=1.0.0 <2.0.0)
- duritong/sysctl (>=0.0.1 <1.0.0)
- stackforge/cinder (>=5.0.0 <6.0.0)
- stackforge/glance (>=5.0.0 <6.0.0)
- puppetlabs/inifile (>=1.0.0 <2.0.0)
- stackforge/keystone (>=5.0.0 <6.0.0)
- puppetlabs/rabbitmq (>=2.0.2 <4.0.0)
- puppetlabs/stdlib (>=4.0.0 <5.0.0)
- stackforge/openstacklib (>=5.0.0 <6.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. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.