da0cedce6f
According to python-django-horizon's SPEC file log file should be owned by user 'apache'. According to openstack-dashboard.conf file located in the same package WSGIProcessGroup should be 'dashboard' and the name should be identical as WSGIDaemonProcess' name. It is required to set /var/run/wsgi as WSGISocketPrefix. [1] http://modwsgi.readthedocs.org/en/latest/configuration-directives/WSGIDaemonProcess.html Change-Id: I9aca382798c7ab37e267c9988b3947e1b3780712 |
||
---|---|---|
manifests | ||
spec | ||
templates | ||
.fixtures.yml | ||
.gitignore | ||
.gitreview | ||
Gemfile | ||
LICENSE | ||
Modulefile | ||
Rakefile | ||
README.md |
horizon
Table of Contents
- Overview - What is the horizon module?
- Module Description - What does the module do?
- Setup - The basics of getting started with horizon
- 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
- Release Notes - Notes on the most recent updates to the module
Overview
The horizon module is a part of Stackforge, an effort by the Openstack infrastructure team to provide continuous integration testing and code review for Openstack and Openstack community projects not part of the core software. The module its self is used to flexibly configure and manage the dashboard service for Openstack.
Module Description
The horizon module is a thorough attempt to make Puppet capable of managing the entirety of horizon. Horizon is a fairly classic django application, which results in a fairly simply Puppet module.
This module is tested in combination with other modules needed to build and leverage an entire Openstack software stack. These modules can be found, all pulled together in the openstack module.
Setup
What the horizon module affects
- horizon, the dashboard service for Openstack.
Installing horizon
example% puppet module install puppetlabs/horizon
Beginning with horizon
To utilize the horizon module's functionality you will need to declare multiple resources but you'll find that doing so is much less complicated than the other OpenStack component modules. The following is a modified excerpt from the openstack module. We recommend you consult and understand the openstack module and the core openstack documentation.
Define a horizon dashboard
class { 'memcached':
listen_ip => '127.0.0.1',
tcp_port => '11211',
udp_port => '11211',
}
class { '::horizon':
cache_server_ip => '127.0.0.1',
cache_server_port => '11211',
secret_key => '12345',
swift => false,
django_debug => 'True',
api_result_limit => '2000',
}
Implementation
horizon
Horizon is a simple module using the combination of a package, template, and the file_line type. Most all the configuration lives inside the included local_settings template and the file_line type is for selectively inserting needed lines into configuration files that aren't explicitly managed by the horizon module.
Limitations
- Only supports Apache using mod_wsgi.
Development
Developer documentation for the entire puppet-openstack project.
Contributors
Release Notes
3.1.0
- Added option parameterize OPENSTACK_NEUTRON_NETWORK settings.
3.0.1
- Adds COMPRESS_OFFLINE option to local_settings to fix broken Ubuntu installation.
3.0.0
- Major release for OpenStack Havana.
- Updated user and group for Debian family OSes.
- Updated policy files for RedHat family OSes.
- Enabled SSL support with cert/key.
- Improved default logging configuration.
- Fixed bug to set LOGOUT_URL properly.
- Introduced new parameters: keystone_url, help_url, endpoint type.
- Fixed user/group regression for Debian.
- Changed keystone_default_role to member.
2.2.0
- Fixed apache 0.9.0 incompatability.
- Various lint fixes.
2.1.0
- Updated local_settings.py.
- Pinned Apache module version.
- Various lint fixes.
2.0.0
- Upstream is now part of stackforge.
- httpd config now managed on every platform.
- Provides option to enable Horizon's display of block device mount points.