OpenStack Nova Puppet Module
Go to file
Jiri Podivin 079d6f48b6 setuptools: Disable auto discovery
The latest release of setuptools 61.0 made a breaking change[1] and
because of this change 'pip install' fails with the following error.

~~~
error: Multiple top-level packages discovered in a flat-layout:
['lib', 'spec', 'manifests', 'releasenotes'].
~~~

Users that don't set 'packages', 'py_modules', or configuration'
are still likely to observe the auto-discovery behavior, which may
halt the build if the project contains multiple directories and/or
multiple Python files directly under the project root.

To disable auto discovery, one can do below in setup.py

~~~
setuptools.setup(..,packages=[],..)
~~~

or

~~~
setuptools.setup(..,py_modules=[],..)
~~~

[1] https://github.com/pypa/setuptools/issues/3197

Note setup.py is not used to install puppet modules. However it is used
to generate a release note, thus should be fixed.

Signed-off-by: Jiri Podivin <jpodivin@redhat.com>
Change-Id: I70e28e2eb7a10c2a8d212ad67f2de723f4292c39
2022-03-29 10:40:26 +02:00
doc Update openstackdocstheme to the latest version 2021-09-29 16:06:50 +08:00
examples Convert all class usage to relative names 2019-12-08 23:13:08 +01:00
lib Use system scope credentials in providers 2022-02-21 14:54:47 +00:00
manifests Deprecate old interface to define mdev types 2022-03-18 02:26:01 +09:00
releasenotes Deprecate old interface to define mdev types 2022-03-18 02:26:01 +09:00
spec Remove deprecated nova::compute::vgpu 2022-03-18 02:25:44 +09:00
templates Add nova::compute::provider class to manage custom provider yaml file 2021-03-05 16:19:41 +01:00
.gitignore Dissuade .gitignore references to personal tools 2018-10-08 11:40:36 +08:00
.gitreview OpenDev Migration Patch 2019-04-19 19:26:26 +00:00
.zuul.yaml TripleO jobs: Replace CentOS 8 jobs by CentOS 9 jobs 2022-02-09 22:40:54 +09:00
bindep.txt Add Puppet package to bindep, for module build 2017-10-27 13:14:37 -07:00
CHANGELOG.md trivial: fix a comment typo 2018-04-12 14:02:00 +08:00
CONTRIBUTING.rst [ussuri][goal] Add CONTRIBUTING.rst 2020-05-10 22:44:02 +02:00
Gemfile Use openstack_spec_helper from zuul checkout 2020-08-27 11:47:18 +02:00
LICENSE Update LICENSE 2018-04-06 20:14:47 +08:00
metadata.json Prepare Yoga RC1 2022-03-13 10:25:09 +00:00
Rakefile Use puppet-openstack_spec_helper for Rakefile & spec_helper_acceptance 2016-01-18 09:11:28 -05:00
README.md Update outdate explanation about virt_type 2021-02-01 22:44:03 +09:00
setup.cfg Add information technology in the setup.cfg 2021-10-01 06:54:49 +08:00
setup.py setuptools: Disable auto discovery 2022-03-29 10:40:26 +02:00
tox.ini Stop configuring install_command in tox. 2021-09-29 18:13:19 +09:00

Team and repository tags

Team and repository tags

nova

Table of Contents

  1. Overview - What is the nova module?
  2. Module Description - What does the module do?
  3. Setup - The basics of getting started with nova
  4. Implementation - An under-the-hood peek at what the module is doing
  5. Limitations - OS compatibility, etc.
  6. Development - Guide for contributing to the module
  7. Release Notes - Release notes for the project
  8. Contributors - Those with commits
  9. 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