65 lines
2.1 KiB
YAML
65 lines
2.1 KiB
YAML
options:
|
|
openstack-origin:
|
|
default: distro
|
|
type: string
|
|
description: |
|
|
Repository from which to install. May be one of the following:
|
|
distro (default), ppa:somecustom/ppa, a deb url sources entry,
|
|
or a supported Cloud Archive release pocket.
|
|
|
|
Supported Cloud Archive sources include: cloud:precise-folsom,
|
|
cloud:precise-folsom/updates, cloud:precise-folsom/staging,
|
|
cloud:precise-folsom/proposed.
|
|
|
|
Note that updating this setting to a source that is known to
|
|
provide a later version of OpenStack will trigger a software
|
|
upgrade.
|
|
database-user:
|
|
default: heat
|
|
type: string
|
|
description: Username for database access
|
|
database:
|
|
default: heat
|
|
type: string
|
|
description: Database name
|
|
region:
|
|
default: RegionOne
|
|
type: string
|
|
description: OpenStack Region
|
|
rabbit-user:
|
|
default: heat
|
|
type: string
|
|
description: Username to request access on rabbitmq-server.
|
|
rabbit-vhost:
|
|
default: openstack
|
|
type: string
|
|
description: RabbitMQ virtual host to request access on rabbitmq-server.
|
|
encryption-key:
|
|
default: ""
|
|
type: string
|
|
description: Encryption key used for authentication info in database
|
|
use-syslog:
|
|
type: boolean
|
|
default: False
|
|
description: |
|
|
By default, all services will log into their corresponding log files.
|
|
Setting this to True will force all services to log to the syslog.
|
|
# Per-service HTTPS configuration.
|
|
ssl_cert:
|
|
type: string
|
|
default:
|
|
description: |
|
|
SSL certificate to install and use for API ports. Setting this value
|
|
and ssl_key will enable reverse proxying, point Heat's entry in the
|
|
Keystone catalog to use https, and override any certficiate and key
|
|
issued by Keystone (if it is configured to do so).
|
|
ssl_key:
|
|
type: string
|
|
default:
|
|
description: SSL key to use with certificate specified as ssl_cert.
|
|
ssl_ca:
|
|
type: string
|
|
default:
|
|
description: |
|
|
SSL CA to use with the certificate and key provided - this is only
|
|
required if you are providing a privately signed ssl_cert and ssl_key. |