d09868a59c
A recent change in Nova enforced end-users to configure neutron notifications using Keystone v3 API. This patch: * deprecates neutron_default_tenant_id. Switch default to 'undef' but still allow to configure the value for backward compatibility. * rename neutron_tenant_name to neutron_project_name. This is not backward compatible within Mitaka cycle, but it is between Liberty & Mitaka. * Add 2 new domain-related parameters: neutron_user_domain_name and neutron_project_domain_name, both defaults to 'Default'. * Add /v3 for neutron_auth_url parameter. It's now required in Nova. The parameter can still be changed if users want to run v2 (before Mitaka) but it will break at some point. Co-Authored-By: David Moreau Simard <dms@redhat.com> Co-Authored-By: Emilien Macchi <emilien@redhat.com> Change-Id: I1a99a050ba70399f045930e26e52719bb53a75b3 Related-Bug: #1542486
nova
7.0.0 - 2015.2.0 - Liberty
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
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',
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.
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/verbose' :
value => true,
}
This will write verbose=true 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, xenserver and vmware compute drivers.
- Tested on EL and Debian derivatives.
Development
Developer documentation for the entire puppet-openstack project.
Beaker-Rspec
This module has beaker-rspec tests
To run the tests on the default vagrant node:
bundle install
bundle exec rspec spec/acceptance
For more information on writing and running beaker-rspec tests visit the documentation: