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-nova', '25.0.0'
Learn more about managing modules with a PuppetfileDocumentation
Team and repository tags
nova
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
- Release Notes - Release notes for the project
- Contributors - Those with commits
- Repository - The project source code repository
Overview
The nova 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 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.
Setup
What the nova module affects:
- Nova, the compute service for OpenStack.
Installing nova
puppet module install openstack/nova
Beginning with nova
To utilize the nova 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.
class { 'nova':
database_connection => 'mysql://nova:a_big_secret@127.0.0.1/nova?charset=utf8',
api_database_connection => 'mysql://nova:a_big_secret@127.0.0.1/nova_api?charset=utf8',
default_transport_url => 'rabbit://nova:an_even_bigger_secret@127.0.0.1:5672/nova',
}
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.
Types
nova_config
The nova_config
provider is a children of the ini_setting provider. It allows one to write an entry in the /etc/nova/nova.conf
file.
nova_config { 'DEFAULT/my_ip' :
value => '192.0.2.1',
}
This will write 'my_ip=192.0.2.1' in the [DEFAULT]
section.
name
Section/setting name to manage from nova.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
- Supports libvirt and vmware compute drivers.
- Tested on EL and Debian derivatives.
Development
Developer documentation for the entire puppet-openstack project.
Release Notes
Contributors
Repository
8.0.0 and beyond
From 8.0.0 release and beyond, release notes are published on docs.openstack.org.
##2015-11-25 - 7.0.0 ###Summary
This is a backwards-incompatible major release for OpenStack Liberty.
####Backwards-incompatible changes
- change section name for AMQP qpid parameters
- change section name for AMQP rabbit parameters
- remove deprecated mysql_module
- do not manage python-greenlet anymore
- rabbitmq: do not manage rabbitmq service anymore
- remove openstackocci installation feature
- enable nova service by default
####Features
- add tag to package and service resources
- add nova::db::sync
- add an ability to manage use_stderr parameter
- reflect provider change in puppet-openstacklib
- add nameservers (dns) parameters
- move os_region_name config option
- use auth_nova method to create nova network
- api: add default_floating_pool parameter
- db: Use postgresql lib class for psycopg package
- add support for RabbitMQ connection heartbeat
- move cinder_catalog_info to init
- don't add non-existent hosts to host aggregates
- make libvirt migration security configurable
- add region support to nova providers
- floating IP range support in Nova network
- rename neutron/url_timeout to neutron/timeout
- add upgrade_levels configuration options
- switch nova to leverage os_package_type fact
- use os_package_type for libvirt service name
- making instance_name_template configurable
- remove POSIX users, groups, and file modes
- allows the modification of the nova-api ports
- put all the logging related parameters to the logging class
- add kombu_reconnect_delay option
- update nova::db class to match other module pattern
- volume: allow to change catalog_info
- add config_drive_format option to nova_compute
- handle libvirt/cpu_model option
- add ability to set default baremetal filters
####Bugfixes
- rely on autorequire for config resource ordering
- avoid empty notification driver
- fixed issue with rabbit_hosts parameter
- docfix: update default image_service param in doc
####Maintenance
- fix rspec 3.x syntax
- acceptance: enable debug & verbosity for OpenStack logs
- initial msync run for all Puppet OpenStack modules
- try to use zuul-cloner to prepare fixtures
- remove class_parameter_defaults puppet-lint check
- acceptance: use common bits from puppet-openstack-integration
- spec: enable webmock connect to IPv4 link-local
##2015-10-10 - 6.1.0 ###Summary
This is a feature and maintenance release in the Kilo series.
####Features
- Allow to change archive destination
- Support allow_start and allow_end parameters
- Add ability to override compute_driver
####Maintenance
- acceptance: checkout stable/kilo puppet modules
- Remove dead nova providers
- Remove very old xenserver configs
##2015-07-08 - 6.0.0 ###Summary
This is a backwards-incompatible major release for OpenStack Kilo.
####Backwards-incompatible changes
- Remove deprecated parameters
- Disable file injection when using RBD as compute ephemeral storage
- Remove Python Package Declaration
- move setting of novncproxy_base_url
- Move rabbit/kombu settings to oslo_messaging_rabbit section
- MySQL: change default MySQL collate to utf8_general_ci
- Moved spice configuration options from DEFAULT to spice section
####Features
- Puppet 4.x support
- Refactorise Keystone resources management
- Configure database parameters on the right nodes
- Add parameters for availability zones configuration
- Migrate postgresql backend to use openstacklib::db::postgresql
- Allow auth_name and auth_name_v3 to be the same
- Add an option to not configure RabbitMQ service
- Database: add slave_connection support
- Support for heal_instance_info_cache_interval
- Only tag packages with openstack tag
- Add PCI Passthrough/SR-IOV support
- Add support for identity_uri
- IPv6 support for migration check
- Allow libvirt secret key setting from param
- Adds OracleLinux support
- Ensure /etc/nova exists before creating secret.xml
- Run db-sync if nova packages are upgraded
- Make package 'bridge-utils' install optional
- Introduce public_url, internal_url and admin_url (and v3/ec2)
- Better handling of package dependencies in nova generic_service
- Add scheduler_driver parameter to nova::scheduler class
- Add parameter to control use of rbd for the ephemeral storage
- Install only required libvirt packages
- keystone/auth: make service description configurable
####Bugfixes
- Fix catalog compilation when not configuring endpoint
- Fix behaviour of 'set-secret-value virsh' exec
- Fix variable access in RBD secret template
####Maintenance
- Acceptance tests with Beaker
- Fix spec tests for RSpec 3.x and Puppet 4.x
##2015-06-17 - 5.1.0 ###Summary
This is a feature and bugfix release in the Juno series.
####Features
- Added parameters for availability zones configuration
- IPv6 support for migration check
- Database: add slave_connection support
- supporting lxc cpu mode
- Add serialproxy configuration
- Switch to TLSv1 as SSLv3 is considered insecure and is disabled by default
- Add PCI Passthrough/SR-IOV support
- Add Ironic support into nova puppet modules
####Bugfixes
- Move setting of novncproxy_base_url
- 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
- Make group on /var/log/nova OS specific
- 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
- virsh returns a list of secret uuids, not keyring names
- Disable file injection when using RBD as compute ephemeral storage
- Correct section for cell_type nova.conf parameter
- crontab: ensure the script is run with shell
- Configure database parameters on the right nodes
####Maintenance
- Pin puppetlabs-concat to 1.2.1 in fixtures
- Pin fixtures for stables branches
- spec: pin rspec-puppet to 1.0.1
##2014-11-24 - 5.0.0 ###Summary
This is a backwards-incompatible major release for OpenStack Juno.
####Backwards-incompatible changes
- Update the [glance] and [neutron] section parameters for Juno
- Bump stdlib dependency to >=4.0.0
- Update nova quota parameters for Juno
- Migrate the ceilometer::db::mysql class to use openstacklib::db::mysql, adding new dependency on openstacklib
- Removed deprecation notice for sectionless nova_config names
####Features
- Add tags to all nova packages
- Add parameter dhcp_domain to nova class
- Add parameters for nova service validation to nova::api
- Add nova::policy to control policy.json
- Add force_raw_images parameter to nova::compute class
- Add parameter ec2_workers to nova::api
- Add parameter rabbit_ha_queues to nova class
- Add parameter pool to nova_floating type
- Add parameters to control whether to configure keystone users
- Add nova::cron::archive_deleted_rows class to create a crontab for archiving deleted database rows
- Add parameter keystone_ec2_url to nova::api
- Add the ability to override the keystone service name in ceilometer::keystone::auth
- Add parameter workers to in nova::conductor and deprecate conductor_workers in nova::api
- Add parameter vnc_keymap in nova::compute
- Add parameter osapi_v3 to nova::api
####Bugfixes
- Fix potential duplicate declaration errors for sysctl::value in nova::network
- Fix dependency cycle in nova::migration::libvirt
- Update the libvirtd init script path for Debian
- Fix the rabbit_virtual_host default in nova::cells
- Fix bug in usage of --vlan versus --vlan_start in nova_network provider
- Change the keystone_service to only be configured if the endpoint is to be configured
- Remove dynamic scoping of File resources in nova class
####Maintenance
- Replace usage of the keyword type with the string 'type' since type is a reserved keyword in puppet 3.7
##2014-11-17 - 4.2.0 ###Summary
This is a feature and bugfix release in the Icehouse series.
####Features
- Add option to configure libvirt service name via class parameters
- Add support for multiple SSL APIs
- Add option to configure os_region_name in the nova config
- Add class for extended logging options
####Bugfixes
- Correct resource dependencies on the nova user
- Fix os version fact comparison for RedHat-based operating systems for specifying service provider
- Fix ssl parameter requirements when using kombu and rabbit
##2014-06-20 - 4.1.0 ###Summary
This is a feature and bugfix release in the Icehouse series.
####Features
- Add API v3 endpoint support
- Add configuration of rbd keyring name
- Add support for run Nova SSL endpoints
####Bugfixes
- Update RabbitMQ dependency
- Update mysql charset to UTF8
####Maintenance
- Pin major gems
##2014-05-01 - 4.0.0 ###Summary
This is a major release for OpenStack Icehouse but contains no API-breaking changes.
####Features
- Add support for RHEL 7
- Add support for metadata and conductor workers
- Add support for vif_plugging parameters
- Add support for puppetlabs-mysql 2.2 and greater
- Add support for instance_usage_audit parameters
- Add support to manage the nova uid/gid for NFS live migration
- Add nova::config to handle additional custom options
- Add support to disable installation of nova utilities
- Add support for durable RabbitMQ queues
- Add SSL support for RabbitMQ
- Add support for nova-objectstore bind address
####Bugfixes
- Update support for notification parameters
- Fix packaging bugs
- Fix report_interval configuration
- Fix file location for nova compute rbd secret
##2014-04-15 - 3.2.1 ###Summary
This is a bugfix release in the Havana series.
####Bugfixes
- Fix consoleauth/spice resource duplication on Red Hat systems
##2014-03-26 - 3.2.0 ###Summary
This is a feature and bugfix release in the Havana series.
####Features
- Deprecate logdir parameter in favor of log_dir
- Allow log_dir to be set to false in order to disable file logging
- Add RBD backend support for VM image storage
- Parameterize libvirt cpu_mode and disk_cachemodes
- Add support for https auth endpoints
- Add ability to disable installation of nova utilities
####Bugfixes
- Replace pip with native package manager for VMWare
- Enable libvirt at boot
##2014-02-14 - 3.1.0 ###Summary
This is a bugfix release in the Havana series.
####Bugfixes
- Add libguestfs-tools package to nova utilities
- Fix vncproxy package naming for Ubuntu
- Fix libvirt configuration
##2014-01-13 - 3.0.0 ###Summary
This is a backwards-incompatible major release for OpenStack Havana.
####Backwards-incompatible changes
- Remove api-paste.ini configuration
####Features
- Add support for live migrations with using the libvirt Nova driver
- Add support for VMWareVCDriver
####Bugfixes
- Fix bug to ensure keystone endpoint is set before service is started
- Fix nova-spiceproxy support on Ubuntu
##2013-10-07 - 2.2.0 ###Summary
This is a feature and bugfix release in the Grizzly series.
####Features
- Add a check to install bridge-utils only if needed
- Add syslog support
- Add installation of pm-utils for VM power management support
####Bugfixes
- Fix cinder include dependency bug
##2013-08-07 - 2.1.0 ###Summary
This is a feature and bugfix release in the Grizzly series.
####Features
- Add support for X-Forwarded-For HTTP Headers
- Add html5 spice support
- Add config drive support
- Add RabbitMQ clustering support
- Add memcached support
- Add SQL idle timeout support
####Bugfixes
- Fix allowed_hosts/database connection bug
####Maintenance
- Pin RabbitMQ and database module versions
##2013-06-24 - 2.0.0 ###Summary
Initial release on StackForge.
####Features
- 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
Dependencies
- puppetlabs/inifile (>=2.0.0 <7.0.0)
- openstack/ironic (>=25.0.0 <26.0.0)
- openstack/keystone (>=25.0.0 <26.0.0)
- puppetlabs/stdlib (>=5.0.0 <10.0.0)
- openstack/openstacklib (>=25.0.0 <26.0.0)
- openstack/oslo (>=25.0.0 <26.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.