eabbcd391e
CentOS 9 Stream recently bumped libvirt version (from 9.0.0 to 9.3.0) and the latest libvirt package no longer requires the daemon package which provides the monolithic libvirt daemon[1] [1]5358618b1cBackport note: This fix is adjusted during backport, because the commit[2] which added support for customizing package status is not present in stable/zed and older branches. [2]ec7b9f29b4Change-Id: I612856bfd23f980b1e94815d3b5e15e0ea39f72e (cherry picked from commit5fe2ca84b0) (cherry picked from commitd1bb160e40) (cherry picked from commitb9720fd43a) (cherry picked from commit83f3820f9c)
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.