Takashi Kajinami 7f7e1010ef Do not use system scope tokens in providers
This is partial revert of 0ed626e1461fecc4f443fcd543a99ba945539b1f .

After discussing several problems caused by scope separation, we
decided to suspend implementing the scope enforcement and focus on
project personas like reader role. As the result of that decision,
the system admin persona will be removed, thus we should use
the project admin persona instead. The previous policy rules to allow
system scope access have been reverted by [1].

This does not revert the original patch to keep the unit tests which
were hugely refactored by that change.

[1] 066e1e69d1394839a9f0bde4ca8c3a0db2d52396

Change-Id: I85847850602ab3526d2fdb1a56bb927183198825
2022-10-06 10:37:04 +09:00
2022-05-18 08:26:19 +09:00
2019-04-19 19:26:26 +00:00
2018-04-12 14:02:00 +08:00
2018-04-06 20:14:47 +08:00
2022-03-29 10:40:26 +02: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

Description
OpenStack Nova Puppet Module
Readme 36 MiB
Languages
Ruby 56.6%
Puppet 42.1%
Python 1.1%
Pascal 0.1%