OpenStack(二)之Horizon——local_settings.py

最新推荐文章于 2024-05-23 23:42:35 发布

前端Baymax

最新推荐文章于 2024-05-23 23:42:35 发布

阅读量2.1k

点赞数

CC 4.0 BY-SA版权

分类专栏： openstack 文章标签： openstack horizon local_setting python

本文链接：https://blog.csdn.net/XXJ19950917/article/details/82347988

本文主要探讨OpenStack的Horizon组件中local_settings.py的配置。官方提供了一些基本参数的说明，而在本地环境中，local_settings文件用于定制化Horizon的各项设置。通过了解和调整这个文件，可以更好地适配和管理OpenStack的用户界面。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

OpenStack(二)之Horizon——local_settings.py

官网上的local_settings.py

local_settings.py
官网给出了基本的配置参数说明，查看基本的参数配置说明可以参照以上的链接进行查看。

本地的local_settings.py

local_settings文件的大致说明

# 在Python文件开头(一般是第一行或者是第二行), 用来说明你的Python源文件所使用的编码。
# 缺省情况下你的程序需要使用ascii码来写, 但如果在其中写中文的话, Python解释器一般会报错, 
# 但如果加上你所用的文件编码, Python就会自动进行处理不会报错。
# -*- coding: utf-8 -*-

# Miscellanous operating system interfaces(其他操作系统接口)
import os

# 国际化与本地化
from django.utils.translation import ugettext_lazy as _

# exceptions引入文件为easystack_dashboard/excepetions.py文件
from easystack_dashboard import exceptions

# DEBUG = True时, 如果出现Bug便于我们看见问题所在, 
# 但是部署时最好不要让用户看见bug的详情, 可能一些不怀好心的人攻击网站, 造成不必要的麻烦。
DEBUG = True

# WEBROOT is the location relative to Webserver root
# should end with a slash.
WEBROOT = '/'

# 现场项目的名称, 比如SCG Cloud是针对于南方电网的项目名称, SG-COS是针对于国网项目的名称。
SITE_BRANDING = 'SCG Cloud'

# LOGIN_URL = WEBROOT + 'auth/login/'
# LOGOUT_URL = WEBROOT + 'auth/logout/'
#
# LOGIN_REDIRECT_URL can be used as an alternative for
# HORIZON_CONFIG.user_home, if user_home is not set.
# Do not set it to '/home/', as this will cause circular redirect loop
# LOGIN_REDIRECT_URL = WEBROOT


# Required for Django 1.5.
# If horizon is running in production (DEBUG is False), set this
# with the list of host/domain names that the application can serve.
# For more information see:
# https://docs.djangoproject.com/en/dev/ref/settings/#allowed-hosts
ALLOWED_HOSTS = ['*', ]

# Set SSL proxy settings:
# For Django 1.4+ pass this header from the proxy after terminating the SSL,
# and don't forget to strip it from the client's request.
# For more information see:
# https://docs.djangoproject.com/en/1.4/ref/settings/#secure-proxy-ssl-header
#SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTOCOL', 'https')

# If Horizon is being served through SSL, then uncomment the following two
# settings to better secure the cookies from security exploits
#CSRF_COOKIE_SECURE = True
#SESSION_COOKIE_SECURE = True

# This setting controls whether or not compression is enabled. Disabling
# compression makes Horizon considerably slower, but makes it much easier
# to debug JS and CSS changes
COMPRESS_ENABLED = True

# Overrides for OpenStack API versions. Use this setting to force the
# OpenStack dashboard to use a specific API version for a given service API.
# Versions specified here should be integers or floats, not strings.
# NOTE: The version should be formatted as it appears in the URL for the
# service API. For example, The identity service APIs have inconsistent
# use of the decimal point, so valid options would be 2.0 or 3.
OPENSTACK_API_VERSIONS = {
    # "data-processing": 1.1,
    "identity": 3,
    # "volume": 2,
}

# Set this to True if running on multi-domain model. When this is enabled, it
# will require user to enter the Domain name in addition to username for login.
#OPENSTACK_KEYSTONE_MULTIDOMAIN_SUPPORT = False

# Overrides the default domain used when running on single-domain model
# with Keystone V3. All entities will be created in the default domain.
OPENSTACK_KEYSTONE_DEFAULT_DOMAIN = 'default'

# Set Console type:
# valid options would be "AUTO"(default), "VNC", "SPICE", "RDP", "SERIAL" or None
# Set to None explicitly if you want to deactivate the console.
#CONSOLE_TYPE = "AUTO"

# Default OpenStack Dashboard configuration.
HORIZON_CONFIG = {
    'user_home': 'easystack_dashboard.views.get_user_home', # views.py中get_user_home函数(判断属于当前用户的主页)
    'ajax_queue_limit': 10, # ajax请求消息队列的时间限制长度
    'auto_fade_alerts': { # 
        'delay': 3000,
        'fade_duration': 1500,
        'types': ['alert-success', 'alert-info']
    },
    'help_url': "http://docs.openstack.org",
    'exceptions': {
  
  'recoverable': exceptions.RECOVERABLE,
                   'not_found': exceptions.NOT_FOUND,
                   'unauthorized': exceptions.UNAUTHORIZED},
    'modal_backdrop': 'static',
    'angular_modules': [],
    'js_files': [],
    'js_spec_files': [],
}

# Specify a regular expression to validate user passwords.
# HORIZON_CONFIG["password_validator"] = {
   
   
#    "regex": '.*',
#    "help_text": _("Your password does not meet the requirements."),
#}

# Disable simplified floating IP address management for deployments with
# multiple floating IP pools or complex network requirements.
#HORIZON_CONFIG["simple_ip_management"] = False

# Turn off browser autocompletion for forms including the login form and
# the database creation workflow if so desired.
#HORIZON_CONFIG["password_autocomplete"] = "off"

# Setting this to True will disable the reveal button for password fields,
# including on the login form.
#HORIZON_CONFIG["disable_password_reveal"] = False

LOCAL_PATH = os.path.dirname(os.path.abspath(__file__))

# Set custom secret key:
# You can either set it to a specific value or you can let horizon generate a
# default secret key that is unique on this machine, e.i. regardless of the
# amount of Python WSGI workers (if used behind Apache+mod_wsgi): However, there
# may be situations where you would want to set this explicitly, e.g. when
# multiple dashboard instances are distributed on different machines (usually
# behind a load-balancer). Either you have to make sure that a session gets all
# requests routed to the same dashboard instance or you set the same SECRET_KEY
# for all of them.
from horizon.utils import secret_key
SECRET_KEY = secret_key.generate_or_read_from_file(
    os.path.join(LOCAL_PATH, '.secret_key_store'))

# We recommend you use memcached for development; otherwise after every reload
# of the django development server, you will have to login again. To use
# memcached set CACHES to something like
# CACHES = {
   
   
#     'default': {
   
   
#         'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache',
#         'LOCATION': '127.0.0.1:11211',
#     }
# }

CACHES = {
   'default': {
       'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache',
       'LOCATION': '127.0.0.1:11211',
   }
}

# CACHES = {
   
   
#     'default': {
   
   
#         'BACKEND': 'django.core.cache.backends.locmem.LocMemCache',
#     }
# }

# if we enable the invcode charge mode, just set it to true(如果需要启用invcode的收费