
In the origin nova::db::mysql, if the value of $allowed_hosts contains or equals to $host, then puppet will complain duplicate declaration error. This patch is aim to update the allowed_hosts conditonal statement in nova::db::mysql. There are two cases to pass $allowed_hosts to $real_allowed_hosts: - If $allowed_hosts is array,then remove $host from $allowed_hosts; - elsif $allowed_hosts is string and not equivalent to $host; At last, if $real_allowed_hosts is not undef, then run nova::db::mysql::host_access Fix bug 1206444 Change-Id: If018321095e62e1196e0c2e6b623b30acb535020
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
- 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':
sql_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
- Only supports libvirt and xenserver compute drivers.
- Tested on EL and Debian derivatives.
Development
Developer documentation for the entire puppet-openstack project.
Contributors
Release Notes
2.0.0
- Upstream is now part of stackfoge.
- 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 quantum module.
- Config changes can be hidden from Puppet logs.
- Move from deprecated rabbit_notifier to rpc_notifier.
- Various cleanups and bug fixes.