e956eba829
With the creation of the new openstack_config provider, some processing that was done in neutron_config has been centralized in openstack_config. The same logic applies for all the neutron resources that edit a ini-like configuration file. Impacted methods are : * section * setting * separator Also, this commit adds the fact that, when passing a specific string (ensure_absent_val) the provider will behave as if ensure => absent was specified. '<SERVICE DEFAULT>' is the default value for ensure_absent_val. The use case is the following : neutron_config { 'DEFAULT/foo' : value => 'bar' } # will work as usual neutron_config { 'DEFAULT/foo' : value => '<SERVICE DEFAULT>' } # will mean absent That means that all the current : if $myvar { neutron_config { 'DEFAULT/foo' : value => $myvar } } else { neutron_config { 'DEFAULT/foo' : ensure => absent } } can be removed in favor of : neutron_config { 'DEFAULT/foo' : value => $myvar } If for any reason '<SERVICE DEFAULT>' turns out to be a valid value for a specific parameter. One could by pass that doing the following : neutron_config { 'DEFAULT/foo' : value => '<SERVICE DEFAULT>', ensure_absent_val => 'foo' } Change-Id: I3f972ecbde3719fe71a82a64f894d41f6ea7e842 Depends-On: I0eeebde3aac2662cc7e69bfad7f8d2481463a218 |
||
---|---|---|
examples | ||
lib/puppet | ||
manifests | ||
spec | ||
templates | ||
.fixtures.yml | ||
.gitignore | ||
.gitreview | ||
CHANGELOG.md | ||
Gemfile | ||
LICENSE | ||
README.md | ||
Rakefile | ||
metadata.json |
README.md
neutron
6.0.0 - 2015.1 - Kilo
Table of Contents
- Overview - What is the neutron module?
- Module Description - What does the module do?
- Setup - Tha basics of getting started with neutron.
- 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 neutron 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 itself is used to flexibly configure and manage the network service for Openstack.
Module Description
The neutron module is an attempt to make Puppet capable of managing the entirety of neutron. This includes manifests to provision such things as keystone endpoints, RPC configurations specific to neutron, database connections, and network driver plugins. Types are shipped as part of the neutron module to assist in manipulation of the Openstack configuration files.
This module is tested in combination with other modules needed to build and leverage an entire Openstack installation. These modules can be found, all pulled together in the openstack module.
Setup
What the neutron module affects:
- Neutron, the network service for Openstack.
Installing neutron
puppet module install openstack/neutron
Beginning with neutron
To utilize the neutron module's functionality you will need to declare multiple resources. The following is a modified excerpt from the openstack module. It provides an example of setting up an Open vSwitch neutron installation. This is not an exhaustive list of all the components needed. We recommend that you consult and understand the openstack module and the core openstack documentation to assist you in understanding the available deployment options.
# enable the neutron service
class { '::neutron':
enabled => true,
bind_host => '127.0.0.1',
rabbit_host => '127.0.0.1',
rabbit_user => 'neutron',
rabbit_password => 'rabbit_secret',
verbose => false,
debug => false,
}
# configure authentication
class { 'neutron::server':
auth_host => '127.0.0.1', # the keystone host address
auth_password => 'keystone_neutron_secret',
sql_connection => 'mysql://neutron:neutron_sql_secret@127.0.0.1/neutron?charset=utf8',
}
# ml2 plugin with vxlan as ml2 driver and ovs as mechanism driver
class { '::neutron::plugins::ml2':
type_drivers => ['vxlan'],
tenant_network_types => ['vxlan'],
vxlan_group => '239.1.1.1',
mechanism_drivers => ['openvswitch'],
vni_ranges => ['0:300']
}
Other neutron network drivers include:
- dhcp,
- metadata,
- and l3.
Nova will also need to be configured to connect to the neutron service. Setting up the nova::network::neutron
class sets
the network_api_class
parameter in nova to use neutron instead of nova-network.
class { 'nova::network::neutron':
neutron_admin_password => 'neutron_admin_secret',
}
The examples
directory also provides a quick tutorial on how to use this module.
Implementation
neutron
neutron is a combination of Puppet manifest and ruby code to deliver configuration and extra functionality through types and providers.
Types
neutron_config
The neutron_config
provider is a children of the ini_setting provider. It allows one to write an entry in the /etc/neutron/neutron.conf
file.
neutron_config { 'DEFAULT/verbose' :
value => true,
}
This will write verbose=true
in the [DEFAULT]
section.
name
Section/setting name to manage from neutron.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
This module supports the following neutron plugins:
- Open vSwitch with ML2
- linuxbridge with ML2
- cisco-neutron with and without ML2
- NVP
- PLUMgrid
The following platforms are supported:
- Ubuntu 12.04 (Precise)
- Debian (Wheezy)
- RHEL 6
- Fedora 18
Beaker-Rspec
This module has beaker-rspec tests
To run:
bundle install
bundle exec rspec spec/acceptance
Development
The puppet-openstack modules follow the Openstack development model. Developer documentation for the entire puppet-openstack project is at:
Contributors
The github contributor graph.