local_settings.py revision 2521
2521N/A# For Django 1.4+ pass this header from the proxy after terminating the SSL, 2521N/A# and don't forget to strip it from the client's request. 2521N/A# If Horizon is being served through SSL, then uncomment the following two 2521N/A# settings to better secure the cookies from security exploits 2521N/A# Default configuration uses /horizon as the application root. Configure auth 2521N/A# redirects here accordingly. 2521N/A# Default OpenStack Dashboard configuration. 2521N/A 'dashboards': (
'project',
'admin',
'settings',),
2521N/A 'default_dashboard':
'project',
2521N/A 'user_home':
'openstack_dashboard.views.get_user_home',
2521N/A 'types': [
'alert-success',
'alert-info']
2521N/A# Specify a regular expression to validate user passwords. 2521N/A# HORIZON_CONFIG["password_validator"] = { 2521N/A# "help_text": _("Your password does not meet the requirements.") 2521N/A# Disable simplified floating IP address management for deployments with 2521N/A# multiple floating IP pools or complex network requirements. 2521N/A# HORIZON_CONFIG["simple_ip_management"] = False 2521N/A# Turn off browser autocompletion for the login form if so desired. 2521N/A# HORIZON_CONFIG["password_autocomplete"] = "off" 2521N/A# You can either set it to a specific value or you can let horizion generate a 2521N/A# default secret key that is unique on this machine, e.i. regardless of the 2521N/A# amount of Python WSGI workers (if used behind Apache+mod_wsgi): However, there 2521N/A# may be situations where you would want to set this explicitly, e.g. when 2521N/A# multiple dashboard instances are distributed on different machines (usually 2521N/A# behind a load-balancer). Either you have to make sure that a session gets all 2521N/A# requests routed to the same dashboard instance or you set the same SECRET_KEY 2521N/A# We recommend you use memcached for development; otherwise after every reload 2521N/A# of the django development server, you will have to login again. To use 2521N/A# memcached set CACHES to something like 2521N/A# 'BACKEND' : 'django.core.cache.backends.memcached.MemcachedCache', 2521N/A# 'LOCATION' : '127.0.0.1:11211', 2521N/A 'BACKEND' :
'django.core.cache.backends.locmem.LocMemCache' 2521N/A# Send email to the console by default 2521N/A#EMAIL_BACKEND = 'django.core.mail.backends.dummy.EmailBackend' 2521N/A# Configure these for your outgoing email host 2521N/A# EMAIL_HOST = 'smtp.my-company.com' 2521N/A# EMAIL_HOST_USER = 'djangomail' 2521N/A# EMAIL_HOST_PASSWORD = 'top-secret!' 2521N/A# For multiple regions uncomment this configuration, and add (endpoint, title). 2521N/A# Disable SSL certificate checks (useful for self-signed certificates): 2521N/A# OPENSTACK_SSL_NO_VERIFY = True 2521N/A# The OPENSTACK_KEYSTONE_BACKEND settings can be used to identify the 2521N/A# capabilities of the auth backend for Keystone. 2521N/A# If Keystone has been configured to use LDAP as the auth backend then set 2521N/A# can_edit_user to False and name to 'ldap'. 2521N/A# TODO(tres): Remove these once Keystone has an API to identify auth backend. 2521N/A # NOTE: as of Grizzly this is not yet supported in Nova so enabling this 2521N/A # setting will not do anything useful 2521N/A# The OPENSTACK_QUANTUM_NETWORK settings can be used to enable optional 2521N/A# services provided by quantum. Currently only the load balancer service 2521N/A# OPENSTACK_ENDPOINT_TYPE specifies the endpoint type to use for the endpoints 2521N/A# in the Keystone service catalog. Use this setting when Horizon is running 2521N/A# external to the OpenStack environment. The default is 'internalURL'. 2521N/A#OPENSTACK_ENDPOINT_TYPE = "publicURL" 2521N/A# on a single page before providing a paging element (a "more" link) 2521N/A# The timezone of the server. This should correspond with the timezone 2521N/A# of your entire OpenStack installation, and hopefully be in UTC. 2521N/A # When set to True this will disable all logging except 2521N/A # for loggers specified in this configuration dictionary. Note that 2521N/A # if nothing is specified here and disable_existing_loggers is True, 2521N/A # django.db.backends will still log unless it is disabled explicitly. 2521N/A 'class':
'django.utils.log.NullHandler',
2521N/A # Set the level to "DEBUG" for verbose output logging. 2521N/A 'class':
'logging.StreamHandler',
2521N/A # Logging from django.db.backends is VERY verbose, send to null