云计算openstack核心组件——horizon Web管理界面（10）

一、horizon 介绍：

理解 horizon

Horizon 为 Openstack 提供一个 WEB 前端的管理界面 (UI 服务 )通过 Horizone 所提供的 DashBoard 服务 , 管理员可以使用通过 WEB UI 对 Openstack 整体云环境进行管理 , 并可直观看到各种操作结果与运行状态。

 

 

DashBoard 与其他组件的关系

 

 

登陆 Dashboard 界面

启动客户端浏览器，于地址栏输入：

http://Horizone_server_ip/dashboard

 

 

 

二、区域（Region）
1、地理上的概念，可以理解为一个独立的数据中心，每个所定义的区域有自己独立的Endpoint；
2、区域之间是完全隔离的，但多个区域之间共享同一个Keystone和Dashboard(目前Openstack中的Dashboard还不支持多个区域)；
3、除了提供隔离的功能，区域的设计更多侧重地理位置的概念，用户可以选择离自己更新的区域来部署自己的服务,选择不同的区域主要是考虑那个区域更靠近自己，如用户在美国，可以选择离美国更近的区域；
4、区域的概念是由Amazon在AWS中提出,主要是解决容错能力和可靠性；

 

三、可用性区域（Availability Zone）
1、AZ是在Region范围内的再次切分，例如可以把一个机架上的服务器划分为一个AZ，划分AZ是为了提高容灾能力和提供廉价的隔离服务；
2、AZ主要是通过冗余来解决可用性的问题，在Amazon的声明中，Instance不可用是指用户所有AZ中的同一个Instance都不可达才表明不可用；
3、AZ是用户可见的一个概念，并可选择，是物理隔离的，一个AZ不可用不会影响其他的AZ，用户在创建Instance的时候可以选择创建到那些AZ中；

 

四、Host Aggreates
一组具有共同属性的节点集合，如以CPU作为区分类型的一个属性，以磁盘（SSD\SAS\SATA）作为区分类型的一个属性，以OS（Windows\Linux）为作区分类型的一个属性；

 

 

五、Cell

nova为了增加横向扩展以及分布式、大规模（地理位置级别）部署的能力，同时又不增加数据库和消息中间件的复杂度，引入了cell的概念，并引入了nova-cell服务。
1、主要是用来解决OpenStack的扩展性和规模瓶颈；
2、每个Cell都有自己独立的DB和AMQP，不与其他模块共用DB和AMQP,解决了大规模环境中DB和AMQP的瓶颈问题；
3、Cell实现了树形结构（通过消息路由）和分级调度（过滤算法和权重算法），Cell之间通过RPC通讯，解决了扩展性问题；

六、 dashbord 的配置文件：

vim /etc/openstack-dashboard/local_settings

vim /etc/openstack-dashboard/local_settings

# -*- coding: utf-8 -*-

 

import os

 

from django.utils.translation import ugettext_lazy as _

 

 

from openstack_dashboard.settings import HORIZON_CONFIG

 

DEBUG = False

 

 

# WEBROOT is the location relative to Webserver root

# should end with a slash.

WEBROOT = '/dashboard/'

#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

 

# 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 = ['horizon.example.com', 'localhost','*']

 

# Set SSL proxy settings:

# 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/dev/ref/settings/#secure-proxy-ssl-header

#SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', '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

 

# The absolute path to the directory where message files are collected.

# The message file must have a .json file extension. When the user logins to

# horizon, the message files collected are processed and displayed to the user.

#MESSAGES_PATH=None

 

# 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.

# Minimum compute version to get the instance locked status is 2.9.

OPENSTACK_API_VERSIONS = {

#    "data-processing": 1.1,

    "identity": 3,

    "image": 2,

    "volume": 2,

    "compute": 2,

}

 

# Set this to True if running on a multi-domain model. When this is enabled, it

# will require the user to enter the Domain name in addition to the username

# for login.

OPENSTACK_KEYSTONE_MULTIDOMAIN_SUPPORT = True

 

# Overrides the default domain used when running on single-domain model

# with Keystone V3. All entities will be created in the default domain.

# NOTE: This value must be the name of the default domain, NOT the ID.

# Also, you will most likely have a value in the keystone policy file like this

#    "cloud_admin": "rule:admin_required and domain_id:<your domain id>"

# This value must be the name of the domain whose ID is specified there.

OPENSTACK_KEYSTONE_DEFAULT_DOMAIN = 'Default'

 

# Set this to True to enable panels that provide the ability for users to

# manage Identity Providers (IdPs) and establish a set of rules to map

# federation protocol attributes to Identity API attributes.

# This extension requires v3.0+ of the Identity API.

#OPENSTACK_KEYSTONE_FEDERATION_MANAGEMENT = False

 

# Set Console type:

# valid options are "AUTO"(default), "VNC", "SPICE", "RDP", "SERIAL" or None

# Set to None explicitly if you want to deactivate the console.

#CONSOLE_TYPE = "AUTO"

 

# If provided, a "Report Bug" link will be displayed in the site header

# which links to the value of this setting (ideally a URL containing

# information on how to report issues).

#HORIZON_CONFIG["bug_url"] = "http://bug-report.example.com"

 

# Show backdrop element outside the modal, do not close the modal

# after clicking on backdrop.

#HORIZON_CONFIG["modal_backdrop"] = "static"

 

# 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 = '/tmp'

 

# 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.

SECRET_KEY='852c7ef13d000ba1bf5d'

 

# 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

SESSION_ENGINE = 'django.contrib.sessions.backends.cache'

 

CACHES = {

    'default': {

        'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache',

        'LOCATION': 'controller:11211',

    },

}

 

#CACHES = {

#    'default': {

#        'BACKEND': 'django.core.cache.backends.locmem.LocMemCache',

#    },

#}

 

# Send email to the console by default

EMAIL_BACKEND = 'django.core.mail.backends.console.EmailBackend'

# Or send them to /dev/null

#EMAIL_BACKEND = 'django.core.mail.backends.dummy.EmailBackend'

 

# Configure these for your outgoing email host

#EMAIL_HOST = 'smtp.my-company.com'

#EMAIL_PORT = 25

#EMAIL_HOST_USER = 'djangomail'

#EMAIL_HOST_PASSWORD = 'top-secret!'

 

# For multiple regions uncomment this configuration, and add (endpoint, title).

#AVAILABLE_REGIONS = [

#    ('http://cluster1.example.com:5000/v2.0', 'cluster1'),

#    ('http://cluster2.example.com:5000/v2.0', 'cluster2'),

#]

 

OPENSTACK_HOST = "controller"

OPENSTACK_KEYSTONE_URL = "http://%s:5000/v3" % OPENSTACK_HOST

OPENSTACK_KEYSTONE_DEFAULT_ROLE = "user"

 

# Enables keystone web single-sign-on if set to True.

#WEBSSO_ENABLED = False

 

# Determines which authentication choice to show as default.

#WEBSSO_INITIAL_CHOICE = "credentials"

 

# The list of authentication mechanisms which include keystone

# federation protocols and identity provider/federation protocol

# mapping keys (WEBSSO_IDP_MAPPING). Current supported protocol

# IDs are 'saml2' and 'oidc'  which represent SAML 2.0, OpenID

# Connect respectively.

# Do not remove the mandatory credentials mechanism.

# Note: The last two tuples are sample mapping keys to a identity provider

# and federation protocol combination (WEBSSO_IDP_MAPPING).

#WEBSSO_CHOICES = (

#    ("credentials", _("Keystone Credentials")),

#    ("oidc", _("OpenID Connect")),

#    ("saml2", _("Security Assertion Markup Language")),

#    ("acme_oidc", "ACME - OpenID Connect"),

#    ("acme_saml2", "ACME - SAML2"),

#)

 

# A dictionary of specific identity provider and federation protocol

# combinations. From the selected authentication mechanism, the value

# will be looked up as keys in the dictionary. If a match is found,

# it will redirect the user to a identity provider and federation protocol

# specific WebSSO endpoint in keystone, otherwise it will use the value

# as the protocol_id when redirecting to the WebSSO by protocol endpoint.

# NOTE: The value is expected to be a tuple formatted as: (<idp_id>, <protocol_id>).

#WEBSSO_IDP_MAPPING = {

#    "acme_oidc": ("acme", "oidc"),

#    "acme_saml2": ("acme", "saml2"),

#}

 

# The Keystone Provider drop down uses Keystone to Keystone federation

# to switch between Keystone service providers.

# Set display name for Identity Provider (dropdown display name)

#KEYSTONE_PROVIDER_IDP_NAME = "Local Keystone"

# This id is used for only for comparison with the service provider IDs. This ID

# should not match any service provider IDs.

#KEYSTONE_PROVIDER_IDP_ID = "localkeystone"

 

# Disable SSL certificate checks (useful for self-signed certificates):

#OPENSTACK_SSL_NO_VERIFY = True

 

# The CA certificate to use to verify SSL connections

#OPENSTACK_SSL_CACERT = '/path/to/cacert.pem'

 

# The OPENSTACK_KEYSTONE_BACKEND settings can be used to identify the

# capabilities of the auth backend for Keystone.

# If Keystone has been configured to use LDAP as the auth backend then set

# can_edit_user to False and name to 'ldap'.

#

# TODO(tres): Remove these once Keystone has an API to identify auth backend.

OPENSTACK_KEYSTONE_BACKEND = {

    'name': 'native',

    'can_edit_user': True,

    'can_edit_group': True,

    'can_edit_project': True,

    'can_edit_domain': True,

    'can_edit_role': True,

}

 

# Setting this to True, will add a new "Retrieve Password" action on instance,

# allowing Admin session password retrieval/decryption.

#OPENSTACK_ENABLE_PASSWORD_RETRIEVE = False

 

# This setting allows deployers to control whether a token is deleted on log

# out. This can be helpful when there are often long running processes being

# run in the Horizon environment.

#TOKEN_DELETE_DISABLED = False

 

# The Launch Instance user experience has been significantly enhanced.

# You can choose whether to enable the new launch instance experience,

# the legacy experience, or both. The legacy experience will be removed

# in a future release, but is available as a temporary backup setting to ensure

# compatibility with existing deployments. Further development will not be

# done on the legacy experience. Please report any problems with the new

# experience via the Launchpad tracking system.

#

# Toggle LAUNCH_INSTANCE_LEGACY_ENABLED and LAUNCH_INSTANCE_NG_ENABLED to

# determine the experience to enable.  Set them both to true to enable

# both.

#LAUNCH_INSTANCE_LEGACY_ENABLED = True

#LAUNCH_INSTANCE_NG_ENABLED = False

 

# A dictionary of settings which can be used to provide the default values for

# properties found in the Launch Instance modal.

#LAUNCH_INSTANCE_DEFAULTS = {

#    'config_drive': False,

#    'enable_scheduler_hints': True,

#    'disable_image': False,

#    'disable_instance_snapshot': False,

#    'disable_volume': False,

#    'disable_volume_snapshot': False,

#    'create_volume': True,

#}

 

# The Xen Hypervisor has the ability to set the mount point for volumes

# attached to instances (other Hypervisors currently do not). Setting

# can_set_mount_point to True will add the option to set the mount point

# from the UI.

OPENSTACK_HYPERVISOR_FEATURES = {

    'can_set_mount_point': False,

    'can_set_password': False,

    'requires_keypair': False,

    'enable_quotas': True

}

 

# The OPENSTACK_CINDER_FEATURES settings can be used to enable optional

# services provided by cinder that is not exposed by its extension API.

OPENSTACK_CINDER_FEATURES = {

    'enable_backup': False,

}

 

# The OPENSTACK_NEUTRON_NETWORK settings can be used to enable optional

# services provided by neutron. Options currently available are load

# balancer service, security groups, quotas, VPN service.

OPENSTACK_NEUTRON_NETWORK = {

    'enable_router': True,

    'enable_quotas': True,

    'enable_ipv6': True,

    'enable_distributed_router': False,

    'enable_ha_router': False,

    'enable_lb': True,

    'enable_firewall': True,

    'enable_vpn': True,

    'enable_fip_topology_check': True,

 

    # Default dns servers you would like to use when a subnet is

    # created.  This is only a default, users can still choose a different

    # list of dns servers when creating a new subnet.

    # The entries below are examples only, and are not appropriate for

    # real deployments

    # 'default_dns_nameservers': ["8.8.8.8", "8.8.4.4", "208.67.222.222"],

 

    # The profile_support option is used to detect if an external router can be

    # configured via the dashboard. When using specific plugins the

    # profile_support can be turned on if needed.

    'profile_support': None,

    #'profile_support': 'cisco',

 

    # Set which provider network types are supported. Only the network types

    # in this list will be available to choose from when creating a network.

    # Network types include local, flat, vlan, gre, vxlan and geneve.

    # 'supported_provider_types': ['*'],

 

    # You can configure available segmentation ID range per network type

    # in your deployment.

    # 'segmentation_id_range': {

    #     'vlan': [1024, 2048],

    #     'vxlan': [4094, 65536],

    # },

 

    # You can define additional provider network types here.

    # 'extra_provider_types': {

    #     'awesome_type': {

    #         'display_name': 'Awesome New Type',

    #         'require_physical_network': False,

    #         'require_segmentation_id': True,

    #     }

    # },

 

    # Set which VNIC types are supported for port binding. Only the VNIC

    # types in this list will be available to choose from when creating a

    # port.

    # VNIC types include 'normal', 'macvtap' and 'direct'.

    # Set to empty list or None to disable VNIC type selection.

    'supported_vnic_types': ['*'],

}

 

# The OPENSTACK_HEAT_STACK settings can be used to disable password

# field required while launching the stack.

OPENSTACK_HEAT_STACK = {

    'enable_user_pass': True,

}

 

# The OPENSTACK_IMAGE_BACKEND settings can be used to customize features

# in the OpenStack Dashboard related to the Image service, such as the list

# of supported image formats.

#OPENSTACK_IMAGE_BACKEND = {

#    'image_formats': [

#        ('', _('Select format')),

#        ('aki', _('AKI - Amazon Kernel Image')),

#        ('ami', _('AMI - Amazon Machine Image')),

#        ('ari', _('ARI - Amazon Ramdisk Image')),

#        ('docker', _('Docker')),

#        ('iso', _('ISO - Optical Disk Image')),

#        ('ova', _('OVA - Open Virtual Appliance')),

#        ('qcow2', _('QCOW2 - QEMU Emulator')),

#        ('raw', _('Raw')),

#        ('vdi', _('VDI - Virtual Disk Image')),

#        ('vhd', _('VHD - Virtual Hard Disk')),

#        ('vmdk', _('VMDK - Virtual Machine Disk')),

#    ],

#}

 

# The IMAGE_CUSTOM_PROPERTY_TITLES settings is used to customize the titles for

# image custom property attributes that appear on image detail pages.

IMAGE_CUSTOM_PROPERTY_TITLES = {

    "architecture": _("Architecture"),

    "kernel_id": _("Kernel ID"),

    "ramdisk_id": _("Ramdisk ID"),

    "image_state": _("Euca2ools state"),

    "project_id": _("Project ID"),

    "image_type": _("Image Type"),

}

 

# The IMAGE_RESERVED_CUSTOM_PROPERTIES setting is used to specify which image

# custom properties should not be displayed in the Image Custom Properties

# table.

IMAGE_RESERVED_CUSTOM_PROPERTIES = []

 

# Set to 'legacy' or 'direct' to allow users to upload images to glance via

# Horizon server. When enabled, a file form field will appear on the create

# image form. If set to 'off', there will be no file form field on the create

# image form. See documentation for deployment considerations.

#HORIZON_IMAGES_UPLOAD_MODE = 'legacy'

 

# Allow a location to be set when creating or updating Glance images.

# If using Glance V2, this value should be False unless the Glance

# configuration and policies allow setting locations.

#IMAGES_ALLOW_LOCATION = False

 

# OPENSTACK_ENDPOINT_TYPE specifies the endpoint type to use for the endpoints

# in the Keystone service catalog. Use this setting when Horizon is running

# external to the OpenStack environment. The default is 'publicURL'.

#OPENSTACK_ENDPOINT_TYPE = "publicURL"

 

# SECONDARY_ENDPOINT_TYPE specifies the fallback endpoint type to use in the

# case that OPENSTACK_ENDPOINT_TYPE is not present in the endpoints

# in the Keystone service catalog. Use this setting when Horizon is running

# external to the OpenStack environment. The default is None. This

# value should differ from OPENSTACK_ENDPOINT_TYPE if used.

#SECONDARY_ENDPOINT_TYPE = None

 

# The number of objects (Swift containers/objects or images) to display

# on a single page before providing a paging element (a "more" link)

# to paginate results.

API_RESULT_LIMIT = 1000

API_RESULT_PAGE_SIZE = 20

 

# The size of chunk in bytes for downloading objects from Swift

SWIFT_FILE_TRANSFER_CHUNK_SIZE = 512 * 1024

 

# The default number of lines displayed for instance console log.

INSTANCE_LOG_LENGTH = 35

 

# Specify a maximum number of items to display in a dropdown.

DROPDOWN_MAX_ITEMS = 30

 

# The timezone of the server. This should correspond with the timezone

# of your entire OpenStack installation, and hopefully be in UTC.

TIME_ZONE = "UTC"

 

# When launching an instance, the menu of available flavors is

# sorted by RAM usage, ascending. If you would like a different sort order,

# you can provide another flavor attribute as sorting key. Alternatively, you

# can provide a custom callback method to use for sorting. You can also provide

# a flag for reverse sort. For more info, see

# http://docs.python.org/2/library/functions.html#sorted

#CREATE_INSTANCE_FLAVOR_SORT = {

#    'key': 'name',

#     # or

#    'key': my_awesome_callback_method,

#    'reverse': False,

#}

 

# Set this to True to display an 'Admin Password' field on the Change Password

# form to verify that it is indeed the admin logged-in who wants to change

# the password.

#ENFORCE_PASSWORD_CHECK = False

 

# Modules that provide /auth routes that can be used to handle different types

# of user authentication. Add auth plugins that require extra route handling to

# this list.

#AUTHENTICATION_URLS = [

#    'openstack_auth.urls',

#]

 

# The Horizon Policy Enforcement engine uses these values to load per service

# policy rule files. The content of these files should match the files the

# OpenStack services are using to determine role based access control in the

# target installation.

 

# Path to directory containing policy.json files

POLICY_FILES_PATH = '/etc/openstack-dashboard'

 

# Map of local copy of service policy files.

# Please insure that your identity policy file matches the one being used on

# your keystone servers. There is an alternate policy file that may be used

# in the Keystone v3 multi-domain case, policy.v3cloudsample.json.

# This file is not included in the Horizon repository by default but can be

# found at

# http://git.openstack.org/cgit/openstack/keystone/tree/etc/ \

# policy.v3cloudsample.json

# Having matching policy files on the Horizon and Keystone servers is essential

# for normal operation. This holds true for all services and their policy files.

#POLICY_FILES = {

#    'identity': 'keystone_policy.json',

#    'compute': 'nova_policy.json',

#    'volume': 'cinder_policy.json',

#    'image': 'glance_policy.json',

#    'orchestration': 'heat_policy.json',

#    'network': 'neutron_policy.json',

#}

 

# TODO: (david-lyle) remove when plugins support adding settings.

# Note: Only used when trove-dashboard plugin is configured to be used by

# Horizon.

# Trove user and database extension support. By default support for

# creating users and databases on database instances is turned on.

# To disable these extensions set the permission here to something

# unusable such as ["!"].

#TROVE_ADD_USER_PERMS = []

#TROVE_ADD_DATABASE_PERMS = []

 

# Change this patch to the appropriate list of tuples containing

# a key, label and static directory containing two files:

# _variables.scss and _styles.scss

#AVAILABLE_THEMES = [

#    ('default', 'Default', 'themes/default'),

#    ('material', 'Material', 'themes/material'),

#]

 

LOGGING = {

    'version': 1,

    # When set to True this will disable all logging except

    # for loggers specified in this configuration dictionary. Note that

    # if nothing is specified here and disable_existing_loggers is True,

    # django.db.backends will still log unless it is disabled explicitly.

    'disable_existing_loggers': False,

    'formatters': {

        'operation': {

            # The format of "%(message)s" is defined by

            # OPERATION_LOG_OPTIONS['format']

            'format': '%(asctime)s %(message)s'

        },

    },

    'handlers': {

        'null': {

            'level': 'DEBUG',

            'class': 'logging.NullHandler',

        },

        'console': {

            # Set the level to "DEBUG" for verbose output logging.

            'level': 'INFO',

            'class': 'logging.StreamHandler',

        },

        'operation': {

            'level': 'INFO',

            'class': 'logging.StreamHandler',

            'formatter': 'operation',

        },

    },

    'loggers': {

        # Logging from django.db.backends is VERY verbose, send to null

        # by default.

        'django.db.backends': {

            'handlers': ['null'],

            'propagate': False,

        },

        'requests': {

            'handlers': ['null'],

            'propagate': False,

        },

        'horizon': {

            'handlers': ['console'],

            'level': 'DEBUG',

            'propagate': False,

        },

        'horizon.operation_log': {

            'handlers': ['operation'],

            'level': 'INFO',

            'propagate': False,

        },

        'openstack_dashboard': {

            'handlers': ['console'],

            'level': 'DEBUG',

            'propagate': False,

        },

        'novaclient': {

            'handlers': ['console'],

            'level': 'DEBUG',

            'propagate': False,

        },

        'cinderclient': {

            'handlers': ['console'],

            'level': 'DEBUG',

            'propagate': False,

        },

        'keystoneclient': {

            'handlers': ['console'],

            'level': 'DEBUG',

            'propagate': False,

        },

        'glanceclient': {

            'handlers': ['console'],

            'level': 'DEBUG',

            'propagate': False,

        },

        'neutronclient': {

            'handlers': ['console'],

            'level': 'DEBUG',

            'propagate': False,

        },

        'heatclient': {

            'handlers': ['console'],

            'level': 'DEBUG',

            'propagate': False,

        },

        'swiftclient': {

            'handlers': ['console'],

            'level': 'DEBUG',

            'propagate': False,

        },

        'openstack_auth': {

            'handlers': ['console'],

            'level': 'DEBUG',

            'propagate': False,

        },

        'nose.plugins.manager': {

            'handlers': ['console'],

            'level': 'DEBUG',

            'propagate': False,

        },

        'django': {

            'handlers': ['console'],

            'level': 'DEBUG',

            'propagate': False,

        },

        'iso8601': {

            'handlers': ['null'],

            'propagate': False,

        },

        'scss': {

            'handlers': ['null'],

            'propagate': False,

        },

    },

}

 

# 'direction' should not be specified for all_tcp/udp/icmp.

# It is specified in the form.

SECURITY_GROUP_RULES = {

    'all_tcp': {

        'name': _('All TCP'),

        'ip_protocol': 'tcp',

        'from_port': '1',

        'to_port': '65535',

    },

    'all_udp': {

        'name': _('All UDP'),

        'ip_protocol': 'udp',

        'from_port': '1',

        'to_port': '65535',

    },

    'all_icmp': {

        'name': _('All ICMP'),

        'ip_protocol': 'icmp',

        'from_port': '-1',

        'to_port': '-1',

    },

    'ssh': {

        'name': 'SSH',

        'ip_protocol': 'tcp',

        'from_port': '22',

        'to_port': '22',

    },

    'smtp': {

        'name': 'SMTP',

        'ip_protocol': 'tcp',

        'from_port': '25',

        'to_port': '25',

    },

    'dns': {

        'name': 'DNS',

        'ip_protocol': 'tcp',

        'from_port': '53',

        'to_port': '53',

    },

    'http': {

        'name': 'HTTP',

        'ip_protocol': 'tcp',

        'from_port': '80',

        'to_port': '80',

    },

    'pop3': {

        'name': 'POP3',

        'ip_protocol': 'tcp',

        'from_port': '110',

        'to_port': '110',

    },

    'imap': {

        'name': 'IMAP',

        'ip_protocol': 'tcp',

        'from_port': '143',

        'to_port': '143',

    },

    'ldap': {

        'name': 'LDAP',

        'ip_protocol': 'tcp',

        'from_port': '389',

        'to_port': '389',

    },

    'https': {

        'name': 'HTTPS',

        'ip_protocol': 'tcp',

        'from_port': '443',

        'to_port': '443',

    },

    'smtps': {

        'name': 'SMTPS',

        'ip_protocol': 'tcp',

        'from_port': '465',

        'to_port': '465',

    },

    'imaps': {

        'name': 'IMAPS',

        'ip_protocol': 'tcp',

        'from_port': '993',

        'to_port': '993',

    },

    'pop3s': {

        'name': 'POP3S',

        'ip_protocol': 'tcp',

        'from_port': '995',

        'to_port': '995',

    },

    'ms_sql': {

        'name': 'MS SQL',

        'ip_protocol': 'tcp',

        'from_port': '1433',

        'to_port': '1433',

    },

    'mysql': {

        'name': 'MYSQL',

        'ip_protocol': 'tcp',

        'from_port': '3306',

        'to_port': '3306',

    },

    'rdp': {

        'name': 'RDP',

        'ip_protocol': 'tcp',

        'from_port': '3389',

        'to_port': '3389',

    },

}

 

# Deprecation Notice:

#

# The setting FLAVOR_EXTRA_KEYS has been deprecated.

# Please load extra spec metadata into the Glance Metadata Definition Catalog.

#

# The sample quota definitions can be found in:

# <glance_source>/etc/metadefs/compute-quota.json

#

# The metadata definition catalog supports CLI and API:

#  $glance --os-image-api-version 2 help md-namespace-import

#  $glance-manage db_load_metadefs <directory_with_definition_files>

#

# See Metadata Definitions on: http://docs.openstack.org/developer/glance/

 

# TODO: (david-lyle) remove when plugins support settings natively

# Note: This is only used when the Sahara plugin is configured and enabled

# for use in Horizon.

# Indicate to the Sahara data processing service whether or not

# automatic floating IP allocation is in effect.  If it is not

# in effect, the user will be prompted to choose a floating IP

# pool for use in their cluster.  False by default.  You would want

# to set this to True if you were running Nova Networking with

# auto_assign_floating_ip = True.

#SAHARA_AUTO_IP_ALLOCATION_ENABLED = False

 

# The hash algorithm to use for authentication tokens. This must

# match the hash algorithm that the identity server and the

# auth_token middleware are using. Allowed values are the

# algorithms supported by Python's hashlib library.

#OPENSTACK_TOKEN_HASH_ALGORITHM = 'md5'

 

# AngularJS requires some settings to be made available to

# the client side. Some settings are required by in-tree / built-in horizon

# features. These settings must be added to REST_API_REQUIRED_SETTINGS in the

# form of ['SETTING_1','SETTING_2'], etc.

#

# You may remove settings from this list for security purposes, but do so at

# the risk of breaking a built-in horizon feature. These settings are required

# for horizon to function properly. Only remove them if you know what you

# are doing. These settings may in the future be moved to be defined within

# the enabled panel configuration.

# You should not add settings to this list for out of tree extensions.

# See: https://wiki.openstack.org/wiki/Horizon/RESTAPI

REST_API_REQUIRED_SETTINGS = ['OPENSTACK_HYPERVISOR_FEATURES',

                              'LAUNCH_INSTANCE_DEFAULTS',

                              'OPENSTACK_IMAGE_FORMATS',

                              'OPENSTACK_KEYSTONE_DEFAULT_DOMAIN']

 

# Additional settings can be made available to the client side for

# extensibility by specifying them in REST_API_ADDITIONAL_SETTINGS

# !! Please use extreme caution as the settings are transferred via HTTP/S

# and are not encrypted on the browser. This is an experimental API and

# may be deprecated in the future without notice.

#REST_API_ADDITIONAL_SETTINGS = []

 

# DISALLOW_IFRAME_EMBED can be used to prevent Horizon from being embedded

# within an iframe. Legacy browsers are still vulnerable to a Cross-Frame

# Scripting (XFS) vulnerability, so this option allows extra security hardening

# where iframes are not used in deployment. Default setting is True.

# For more information see:

# http://tinyurl.com/anticlickjack

#DISALLOW_IFRAME_EMBED = True

 

# Help URL can be made available for the client. To provide a help URL, edit the

# following attribute to the URL of your choice.

#HORIZON_CONFIG["help_url"] = "http://openstack.mycompany.org"

 

# Settings for OperationLogMiddleware

# OPERATION_LOG_ENABLED is flag to use the function to log an operation on

# Horizon.

# mask_targets is arrangement for appointing a target to mask.

# method_targets is arrangement of HTTP method to output log.

# format is the log contents.

#OPERATION_LOG_ENABLED = False

#OPERATION_LOG_OPTIONS = {

#    'mask_fields': ['password'],

#    'target_methods': ['POST'],

#    'format': ("[%(domain_name)s] [%(domain_id)s] [%(project_name)s]"

#        " [%(project_id)s] [%(user_name)s] [%(user_id)s] [%(request_scheme)s]"

#        " [%(referer_url)s] [%(request_url)s] [%(message)s] [%(method)s]"

#        " [%(http_status)s] [%(param)s]"),

#}

 

# The default date range in the Overview panel meters - either <today> minus N

# days (if the value is integer N), or from the beginning of the current month

# until today (if set to None). This setting should be used to limit the amount

# of data fetched by default when rendering the Overview panel.

#OVERVIEW_DAYS_RANGE = 1

 

# To allow operators to require users provide a search criteria first

# before loading any data into the views, set the following dict

# attributes to True in each one of the panels you want to enable this feature.

# Follow the convention <dashboard>.<view>

#FILTER_DATA_FIRST = {

#    'admin.instances': False,

#    'admin.images': False,

#    'admin.networks': False,

#    'admin.routers': False,

#    'admin.volumes': False,

#    'identity.users': False,

#    'identity.projects': False,

#    'identity.groups': False,

#    'identity.roles': False

#}

 

# Dict used to restrict user private subnet cidr range.

# An empty list means that user input will not be restricted

# for a corresponding IP version. By default, there is

# no restriction for IPv4 or IPv6. To restrict

# user private subnet cidr range set ALLOWED_PRIVATE_SUBNET_CIDR

# to something like

#ALLOWED_PRIVATE_SUBNET_CIDR = {

#    'ipv4': ['10.0.0.0/8', '192.168.0.0/16'],

#    'ipv6': ['fc00::/7']

#}

ALLOWED_PRIVATE_SUBNET_CIDR = {'ipv4': [], 'ipv6': []}

 

# Project and user can have any attributes by keystone v3 mechanism.

# This settings can treat these attributes on Horizon.

# It means, when you show Create/Update modal, attribute below is

# shown and you can specify any value.

# If you'd like to display these extra data in project or user index table,

# Keystone v3 allows you to add extra properties to Project and Users.

# Horizon's customization (http://docs.openstack.org/developer/horizon/topics/customizing.html#horizon-customization-module-overrides)

# allows you to display this extra information in the Create/Update modal and

# the corresponding tables.

#PROJECT_TABLE_EXTRA_INFO = {

#   'phone_num': _('Phone Number'),

#}

#USER_TABLE_EXTRA_INFO = {

#   'phone_num': _('Phone Number'),

#}