bfcBwhAn

1CONFIG_KEYSTONE_ADMIN_EMAIL=root@localhost
2
3# User name for the Identity service 'admin' user.  Defaults to
4# 'admin'.
5CONFIG_KEYSTONE_ADMIN_USERNAME=admin
6
7# Password to use for the Identity service 'admin' user.
8CONFIG_KEYSTONE_ADMIN_PW=2866fcf92d014d41
9
10# Password to use for the Identity service 'demo' user.
11CONFIG_KEYSTONE_DEMO_PW=a34070db41c94a61
12
13# Identity service API version string. ['v2.0', 'v3']
14CONFIG_KEYSTONE_API_VERSION=v3
15
16# Identity service token format (UUID, PKI or FERNET). The
17# recommended format for new deployments is FERNET. ['UUID', 'PKI',
18# 'FERNET']
19CONFIG_KEYSTONE_TOKEN_FORMAT=FERNET
20
21# Type of Identity service backend (sql or ldap). ['sql', 'ldap']
22CONFIG_KEYSTONE_IDENTITY_BACKEND=sql
23
24# URL for the Identity service LDAP backend.
25CONFIG_KEYSTONE_LDAP_URL=ldap://10.1.1.2
26
27# User DN for the Identity service LDAP backend.  Used to bind to the
28# LDAP server if the LDAP server does not allow anonymous
29# authentication.
30CONFIG_KEYSTONE_LDAP_USER_DN=
31
32# User DN password for the Identity service LDAP backend.
33CONFIG_KEYSTONE_LDAP_USER_PASSWORD=
34
35# Base suffix for the Identity service LDAP backend.
36CONFIG_KEYSTONE_LDAP_SUFFIX=
37
38# Query scope for the Identity service LDAP backend. Use 'one' for
39# onelevel/singleLevel or 'sub' for subtree/wholeSubtree ('base' is
40# not actually used by the Identity service and is therefore
41# deprecated). ['base', 'one', 'sub']
42CONFIG_KEYSTONE_LDAP_QUERY_SCOPE=one
43
44# Query page size for the Identity service LDAP backend.
45CONFIG_KEYSTONE_LDAP_PAGE_SIZE=-1
46
47# User subtree for the Identity service LDAP backend.
48CONFIG_KEYSTONE_LDAP_USER_SUBTREE=
49
50# User query filter for the Identity service LDAP backend.
51CONFIG_KEYSTONE_LDAP_USER_FILTER=
52
53# User object class for the Identity service LDAP backend.
54CONFIG_KEYSTONE_LDAP_USER_OBJECTCLASS=
55
56# User ID attribute for the Identity service LDAP backend.
57CONFIG_KEYSTONE_LDAP_USER_ID_ATTRIBUTE=
58
59# User name attribute for the Identity service LDAP backend.
60CONFIG_KEYSTONE_LDAP_USER_NAME_ATTRIBUTE=
61
62# User email address attribute for the Identity service LDAP backend.
63CONFIG_KEYSTONE_LDAP_USER_MAIL_ATTRIBUTE=
64
65# User-enabled attribute for the Identity service LDAP backend.
66CONFIG_KEYSTONE_LDAP_USER_ENABLED_ATTRIBUTE=
67
68# Bit mask integer applied to user-enabled attribute for the Identity
69# service LDAP backend. Indicate the bit that the enabled value is
70# stored in if the LDAP server represents "enabled" as a bit on an
71# integer rather than a boolean. A value of "0" indicates the mask is
72# not used (default). If this is not set to "0", the typical value is
73# "2", typically used when
74# "CONFIG_KEYSTONE_LDAP_USER_ENABLED_ATTRIBUTE = userAccountControl".
75CONFIG_KEYSTONE_LDAP_USER_ENABLED_MASK=-1
76
77# Value of enabled attribute which indicates user is enabled for the
78# Identity service LDAP backend. This should match an appropriate
79# integer value if the LDAP server uses non-boolean (bitmask) values
80# to indicate whether a user is enabled or disabled. If this is not
81# set as 'y', the typical value is "512". This is typically used when
82# "CONFIG_KEYSTONE_LDAP_USER_ENABLED_ATTRIBUTE = userAccountControl".
83CONFIG_KEYSTONE_LDAP_USER_ENABLED_DEFAULT=TRUE
84
85# Specify 'y' if users are disabled (not enabled) in the Identity
86# service LDAP backend (inverts boolean-enalbed values).  Some LDAP
87# servers use a boolean lock attribute where "y" means an account is
88# disabled. Setting this to 'y' allows these lock attributes to be
89# used. This setting will have no effect if
90# "CONFIG_KEYSTONE_LDAP_USER_ENABLED_MASK" is in use. ['n', 'y']
91CONFIG_KEYSTONE_LDAP_USER_ENABLED_INVERT=n
92
93# Comma-separated list of attributes stripped from LDAP user entry
94# upon update.
95CONFIG_KEYSTONE_LDAP_USER_ATTRIBUTE_IGNORE=
96
97# Identity service LDAP attribute mapped to default_project_id for
98# users.
99CONFIG_KEYSTONE_LDAP_USER_DEFAULT_PROJECT_ID_ATTRIBUTE=
100
101# Specify 'y' if you want to be able to create Identity service users
102# through the Identity service interface; specify 'n' if you will
103# create directly in the LDAP backend. ['n', 'y']
104CONFIG_KEYSTONE_LDAP_USER_ALLOW_CREATE=n
105
106# Specify 'y' if you want to be able to update Identity service users
107# through the Identity service interface; specify 'n' if you will
108# update directly in the LDAP backend. ['n', 'y']
109CONFIG_KEYSTONE_LDAP_USER_ALLOW_UPDATE=n
110
111# Specify 'y' if you want to be able to delete Identity service users
112# through the Identity service interface; specify 'n' if you will
113# delete directly in the LDAP backend. ['n', 'y']
114CONFIG_KEYSTONE_LDAP_USER_ALLOW_DELETE=n
115
116# Identity service LDAP attribute mapped to password.
117CONFIG_KEYSTONE_LDAP_USER_PASS_ATTRIBUTE=
118
119# DN of the group entry to hold enabled LDAP users when using enabled
120# emulation.
121CONFIG_KEYSTONE_LDAP_USER_ENABLED_EMULATION_DN=
122
123# List of additional LDAP attributes for mapping additional attribute
124# mappings for users. The attribute-mapping format is
125# <ldap_attr>:<user_attr>, where ldap_attr is the attribute in the
126# LDAP entry and user_attr is the Identity API attribute.
127CONFIG_KEYSTONE_LDAP_USER_ADDITIONAL_ATTRIBUTE_MAPPING=
128
129# Group subtree for the Identity service LDAP backend.
130CONFIG_KEYSTONE_LDAP_GROUP_SUBTREE=
131
132# Group query filter for the Identity service LDAP backend.
133CONFIG_KEYSTONE_LDAP_GROUP_FILTER=
134
135# Group object class for the Identity service LDAP backend.
136CONFIG_KEYSTONE_LDAP_GROUP_OBJECTCLASS=
137
138# Group ID attribute for the Identity service LDAP backend.
139CONFIG_KEYSTONE_LDAP_GROUP_ID_ATTRIBUTE=
140
141# Group name attribute for the Identity service LDAP backend.
142CONFIG_KEYSTONE_LDAP_GROUP_NAME_ATTRIBUTE=
143
144# Group member attribute for the Identity service LDAP backend.
145CONFIG_KEYSTONE_LDAP_GROUP_MEMBER_ATTRIBUTE=
146
147# Group description attribute for the Identity service LDAP backend.
148CONFIG_KEYSTONE_LDAP_GROUP_DESC_ATTRIBUTE=
149
150# Comma-separated list of attributes stripped from LDAP group entry
151# upon update.
152CONFIG_KEYSTONE_LDAP_GROUP_ATTRIBUTE_IGNORE=
153
154# Specify 'y' if you want to be able to create Identity service
155# groups through the Identity service interface; specify 'n' if you
156# will create directly in the LDAP backend. ['n', 'y']
157CONFIG_KEYSTONE_LDAP_GROUP_ALLOW_CREATE=n
158
159# Specify 'y' if you want to be able to update Identity service
160# groups through the Identity service interface; specify 'n' if you
161# will update directly in the LDAP backend. ['n', 'y']
162CONFIG_KEYSTONE_LDAP_GROUP_ALLOW_UPDATE=n
163
164# Specify 'y' if you want to be able to delete Identity service
165# groups through the Identity service interface; specify 'n' if you
166# will delete directly in the LDAP backend. ['n', 'y']
167CONFIG_KEYSTONE_LDAP_GROUP_ALLOW_DELETE=n
168
169# List of additional LDAP attributes used for mapping additional
170# attribute mappings for groups. The attribute=mapping format is
171# <ldap_attr>:<group_attr>, where ldap_attr is the attribute in the
172# LDAP entry and group_attr is the Identity API attribute.
173CONFIG_KEYSTONE_LDAP_GROUP_ADDITIONAL_ATTRIBUTE_MAPPING=
174
175# Specify 'y' if the Identity service LDAP backend should use TLS.
176# ['n', 'y']
177CONFIG_KEYSTONE_LDAP_USE_TLS=n
178
179# CA certificate directory for Identity service LDAP backend (if TLS
180# is used).
181CONFIG_KEYSTONE_LDAP_TLS_CACERTDIR=
182
183# CA certificate file for Identity service LDAP backend (if TLS is
184# used).
185CONFIG_KEYSTONE_LDAP_TLS_CACERTFILE=
186
187# Certificate-checking strictness level for Identity service LDAP
188# backend; valid options are: never, allow, demand. ['never', 'allow',
189# 'demand']
190CONFIG_KEYSTONE_LDAP_TLS_REQ_CERT=demand
191
192# Password to use for the Image service (glance) to access the
193# database.
194CONFIG_GLANCE_DB_PW=304ab1e7f2d747e7
195
196# Password to use for the Image service to authenticate with the
197# Identity service.
198CONFIG_GLANCE_KS_PW=600aa35e10e34b94
199
200# Storage backend for the Image service (controls how the Image
201# service stores disk images). Valid options are: file or swift
202# (Object Storage). The Object Storage service must be enabled to use
203# it as a working backend; otherwise, Packstack falls back to 'file'.
204# ['file', 'swift']
205CONFIG_GLANCE_BACKEND=file
206
207# Password to use for the Block Storage service (cinder) to access
208# the database.
209CONFIG_CINDER_DB_PW=4433826a27354104
210
211# Enter y if cron job for removing soft deleted DB rows should be
212# created.
213CONFIG_CINDER_DB_PURGE_ENABLE=True
214
215# Password to use for the Block Storage service to authenticate with
216# the Identity service.
217CONFIG_CINDER_KS_PW=c1da21d11b594ded
218
219# Storage backend to use for the Block Storage service; valid options
220# are: lvm, gluster, nfs, vmdk, netapp, solidfire. ['lvm', 'gluster',
221# 'nfs', 'vmdk', 'netapp', 'solidfire']
222CONFIG_CINDER_BACKEND=lvm
223
224# Specify 'y' to create the Block Storage volumes group. That is,
225# Packstack creates a raw disk image in /var/lib/cinder, and mounts it
226# using a loopback device. This should only be used for testing on a
227# proof-of-concept installation of the Block Storage service (a file-
228# backed volume group is not suitable for production usage). ['y',
229# 'n']
230CONFIG_CINDER_VOLUMES_CREATE=n
231
232# Specify a custom name for the lvm cinder volume group
233CONFIG_CINDER_VOLUME_NAME=cinder-volumes
234
235# Size of Block Storage volumes group. Actual volume size will be
236# extended with 3% more space for VG metadata. Remember that the size
237# of the volume group will restrict the amount of disk space that you
238# can expose to Compute instances, and that the specified amount must
239# be available on the device used for /var/lib/cinder.
240CONFIG_CINDER_VOLUMES_SIZE=20G
241
242# A single or comma-separated list of Red Hat Storage (gluster)
243# volume shares to mount. Example: 'ip-address:/vol-name', 'domain
244# :/vol-name'
245CONFIG_CINDER_GLUSTER_MOUNTS=
246
247# A single or comma-separated list of NFS exports to mount. Example:
248# 'ip-address:/export-name'
249CONFIG_CINDER_NFS_MOUNTS=
250
251# Administrative user account name used to access the NetApp storage
252# system or proxy server.
253CONFIG_CINDER_NETAPP_LOGIN=
254
255# Password for the NetApp administrative user account specified in
256# the CONFIG_CINDER_NETAPP_LOGIN parameter.
257CONFIG_CINDER_NETAPP_PASSWORD=
258
259# Hostname (or IP address) for the NetApp storage system or proxy
260# server.
261CONFIG_CINDER_NETAPP_HOSTNAME=
262
263# The TCP port to use for communication with the storage system or
264# proxy. If not specified, Data ONTAP drivers will use 80 for HTTP and
265# 443 for HTTPS; E-Series will use 8080 for HTTP and 8443 for HTTPS.
266# Defaults to 80.
267CONFIG_CINDER_NETAPP_SERVER_PORT=80
268
269# Storage family type used on the NetApp storage system; valid
270# options are ontap_7mode for using Data ONTAP operating in 7-Mode,
271# ontap_cluster for using clustered Data ONTAP, or E-Series for NetApp
272# E-Series. Defaults to ontap_cluster. ['ontap_7mode',
273# 'ontap_cluster', 'eseries']
274CONFIG_CINDER_NETAPP_STORAGE_FAMILY=ontap_cluster
275
276# The transport protocol used when communicating with the NetApp
277# storage system or proxy server. Valid values are http or https.
278# Defaults to 'http'. ['http', 'https']
279CONFIG_CINDER_NETAPP_TRANSPORT_TYPE=http
280
281# Storage protocol to be used on the data path with the NetApp
282# storage system; valid options are iscsi, fc, nfs. Defaults to nfs.
283# ['iscsi', 'fc', 'nfs']
284CONFIG_CINDER_NETAPP_STORAGE_PROTOCOL=nfs
285
286# Quantity to be multiplied by the requested volume size to ensure
287# enough space is available on the virtual storage server (Vserver) to
288# fulfill the volume creation request.  Defaults to 1.0.
289CONFIG_CINDER_NETAPP_SIZE_MULTIPLIER=1.0
290
291# Time period (in minutes) that is allowed to elapse after the image
292# is last accessed, before it is deleted from the NFS image cache.
293# When a cache-cleaning cycle begins, images in the cache that have
294# not been accessed in the last M minutes, where M is the value of
295# this parameter, are deleted from the cache to create free space on
296# the NFS share. Defaults to 720.
297CONFIG_CINDER_NETAPP_EXPIRY_THRES_MINUTES=720
298
299# If the percentage of available space for an NFS share has dropped
300# below the value specified by this parameter, the NFS image cache is
301# cleaned.  Defaults to 20.
302CONFIG_CINDER_NETAPP_THRES_AVL_SIZE_PERC_START=20
303
304# When the percentage of available space on an NFS share has reached
305# the percentage specified by this parameter, the driver stops
306# clearing files from the NFS image cache that have not been accessed
307# in the last M minutes, where M is the value of the
308# CONFIG_CINDER_NETAPP_EXPIRY_THRES_MINUTES parameter. Defaults to 60.
309CONFIG_CINDER_NETAPP_THRES_AVL_SIZE_PERC_STOP=60
310
311# Single or comma-separated list of NetApp NFS shares for Block
312# Storage to use.  Format: ip-address:/export-name. Defaults to ''.
313CONFIG_CINDER_NETAPP_NFS_SHARES=
314
315# File with the list of available NFS shares.   Defaults to
316# '/etc/cinder/shares.conf'.
317CONFIG_CINDER_NETAPP_NFS_SHARES_CONFIG=/etc/cinder/shares.conf
318
319# This parameter is only utilized when the storage protocol is
320# configured to use iSCSI or FC. This parameter is used to restrict
321# provisioning to the specified controller volumes. Specify the value
322# of this parameter to be a comma separated list of NetApp controller
323# volume names to be used for provisioning. Defaults to ''.
324CONFIG_CINDER_NETAPP_VOLUME_LIST=
325
326# The vFiler unit on which provisioning of block storage volumes will
327# be done. This parameter is only used by the driver when connecting
328# to an instance with a storage family of Data ONTAP operating in
329# 7-Mode Only use this parameter when utilizing the MultiStore feature
330# on the NetApp storage system. Defaults to ''.
331CONFIG_CINDER_NETAPP_VFILER=
332
333# The name of the config.conf stanza for a Data ONTAP (7-mode) HA
334# partner.  This option is only used by the driver when connecting to
335# an instance with a storage family of Data ONTAP operating in 7-Mode,
336# and it is required if the storage protocol selected is FC. Defaults
337# to ''.
338CONFIG_CINDER_NETAPP_PARTNER_BACKEND_NAME=
339
340# This option specifies the virtual storage server (Vserver) name on
341# the storage cluster on which provisioning of block storage volumes
342# should occur. Defaults to ''.
343CONFIG_CINDER_NETAPP_VSERVER=
344
345# Restricts provisioning to the specified controllers. Value must be
346# a comma-separated list of controller hostnames or IP addresses to be
347# used for provisioning. This option is only utilized when the storage
348# family is configured to use E-Series. Defaults to ''.
349CONFIG_CINDER_NETAPP_CONTROLLER_IPS=
350
351# Password for the NetApp E-Series storage array. Defaults to ''.
352CONFIG_CINDER_NETAPP_SA_PASSWORD=
353
354# This option is used to define how the controllers in the E-Series
355# storage array will work with the particular operating system on the
356# hosts that are connected to it. Defaults to 'linux_dm_mp'
357CONFIG_CINDER_NETAPP_ESERIES_HOST_TYPE=linux_dm_mp
358
359# Path to the NetApp E-Series proxy application on a proxy server.
360# The value is combined with the value of the
361# CONFIG_CINDER_NETAPP_TRANSPORT_TYPE, CONFIG_CINDER_NETAPP_HOSTNAME,
362# and CONFIG_CINDER_NETAPP_HOSTNAME options to create the URL used by
363# the driver to connect to the proxy application. Defaults to
364# '/devmgr/v2'.
365CONFIG_CINDER_NETAPP_WEBSERVICE_PATH=/devmgr/v2
366
367# Restricts provisioning to the specified storage pools. Only dynamic
368# disk pools are currently supported. The value must be a comma-
369# separated list of disk pool names to be used for provisioning.
370# Defaults to ''.
371CONFIG_CINDER_NETAPP_STORAGE_POOLS=
372
373# Cluster admin account name used to access the SolidFire storage
374# system.
375CONFIG_CINDER_SOLIDFIRE_LOGIN=
376
377# Password for the SolidFire cluster admin user account specified in
378# the CONFIG_CINDER_SOLIDFIRE_LOGIN parameter.
379CONFIG_CINDER_SOLIDFIRE_PASSWORD=
380
381# Hostname (or IP address) for the SolidFire storage system's MVIP.
382CONFIG_CINDER_SOLIDFIRE_HOSTNAME=
383
384# Password to use for OpenStack Bare Metal Provisioning (ironic) to
385# access the database.
386CONFIG_IRONIC_DB_PW=PW_PLACEHOLDER
387
388# Password to use for OpenStack Bare Metal Provisioning to
389# authenticate with the Identity service.
390CONFIG_IRONIC_KS_PW=PW_PLACEHOLDER
391
392# Enter y if cron job for removing soft deleted DB rows should be
393# created.
394CONFIG_NOVA_DB_PURGE_ENABLE=True
395
396# Password to use for the Compute service (nova) to access the
397# database.
398CONFIG_NOVA_DB_PW=9bddbd89e43a45a3
399
400# Password to use for the Compute service to authenticate with the
401# Identity service.
402CONFIG_NOVA_KS_PW=c533ef3e2b9b4a67
403
404# Whether or not Packstack should manage a default initial set of
405# Nova flavors. Defaults to 'y'.
406CONFIG_NOVA_MANAGE_FLAVORS=y
407
408# Overcommitment ratio for virtual to physical CPUs. Specify 1.0 to
409# disable CPU overcommitment.
410CONFIG_NOVA_SCHED_CPU_ALLOC_RATIO=16.0
411
412# Overcommitment ratio for virtual to physical RAM. Specify 1.0 to
413# disable RAM overcommitment.
414CONFIG_NOVA_SCHED_RAM_ALLOC_RATIO=1.5
415
416# Protocol used for instance migration. Valid options are: ssh and
417# tcp. Note that the tcp protocol is not encrypted, so it is insecure.
418# ['ssh', 'tcp']
419CONFIG_NOVA_COMPUTE_MIGRATE_PROTOCOL=ssh
420
421# PEM encoded certificate to be used for ssl on the https server,
422# leave blank if one should be generated, this certificate should not
423# require a passphrase. If CONFIG_HORIZON_SSL is set to 'n' this
424# parameter is ignored.
425CONFIG_VNC_SSL_CERT=
426
427# SSL keyfile corresponding to the certificate if one was entered. If
428# CONFIG_HORIZON_SSL is set to 'n' this parameter is ignored.
429CONFIG_VNC_SSL_KEY=
430
431# Enter the PCI passthrough array of hash in JSON style for
432# controller eg. [{"vendor_id":"1234", "product_id":"5678",
433# "name":"default"}, {...}]
434CONFIG_NOVA_PCI_ALIAS=
435
436# Enter the PCI passthrough whitelist array of hash in JSON style for
437# controller eg. [{"vendor_id":"1234", "product_id":"5678",
438# "name':"default"}, {...}]
439CONFIG_NOVA_PCI_PASSTHROUGH_WHITELIST=
440
441# The hypervisor driver to use with Nova. Can be either 'qemu' or
442# 'kvm'. Defaults to 'qemu' on virtual machines and 'kvm' on bare
443# metal hardware. For nested KVM set it explicitly to 'kvm'.
444CONFIG_NOVA_LIBVIRT_VIRT_TYPE=qemu
445
446# Password to use for OpenStack Networking (neutron) to authenticate
447# with the Identity service.
448CONFIG_NEUTRON_KS_PW=7e3b62cd5af24a84
449
450# The password to use for OpenStack Networking to access the
451# database.
452CONFIG_NEUTRON_DB_PW=1afd785d3d1b4490
453
454# The name of the Open vSwitch bridge (or empty for linuxbridge) for
455# the OpenStack Networking L3 agent to use for external  traffic.
456# Specify 'provider' if you intend to use a provider network to handle
457# external traffic.
458CONFIG_NEUTRON_L3_EXT_BRIDGE=br-ex
459
460# Password for the OpenStack Networking metadata agent.
461CONFIG_NEUTRON_METADATA_PW=95b72299912649ba
462
463# Specify 'y' to install OpenStack Networking's Load-Balancing-
464# as-a-Service (LBaaS). ['y', 'n']
465CONFIG_LBAAS_INSTALL=n
466
467# Specify 'y' to install OpenStack Networking's L3 Metering agent
468# ['y', 'n']
469CONFIG_NEUTRON_METERING_AGENT_INSTALL=y
470
471# Specify 'y' to configure OpenStack Networking's Firewall-
472# as-a-Service (FWaaS). ['y', 'n']
473CONFIG_NEUTRON_FWAAS=n
474
475# Specify 'y' to configure OpenStack Networking's VPN-as-a-Service
476# (VPNaaS). ['y', 'n']
477CONFIG_NEUTRON_VPNAAS=n
478
479# Comma-separated list of network-type driver entry points to be
480# loaded from the neutron.ml2.type_drivers namespace. ['local',
481# 'flat', 'vlan', 'gre', 'vxlan', 'geneve']
482CONFIG_NEUTRON_ML2_TYPE_DRIVERS=vxlan,flat
483
484# Comma-separated, ordered list of network types to allocate as
485# tenant networks. The 'local' value is only useful for single-box
486# testing and provides no connectivity between hosts. ['local',
487# 'vlan', 'gre', 'vxlan', 'geneve']
488CONFIG_NEUTRON_ML2_TENANT_NETWORK_TYPES=vxlan
489
490# Comma-separated ordered list of networking mechanism driver entry
491# points to be loaded from the neutron.ml2.mechanism_drivers
492# namespace. ['logger', 'test', 'linuxbridge', 'openvswitch',
493# 'hyperv', 'ncs', 'arista', 'cisco_nexus', 'mlnx', 'l2population',
494# 'sriovnicswitch', 'ovn']
495CONFIG_NEUTRON_ML2_MECHANISM_DRIVERS=openvswitch
496
497# Comma-separated list of physical_network names with which flat
498# networks can be created. Use * to allow flat networks with arbitrary
499# physical_network names.
500CONFIG_NEUTRON_ML2_FLAT_NETWORKS=*
501
502# Comma-separated list of <physical_network>:<vlan_min>:<vlan_max> or
503# <physical_network> specifying physical_network names usable for VLAN
504# provider and tenant networks, as well as ranges of VLAN tags on each
505# available for allocation to tenant networks.
506CONFIG_NEUTRON_ML2_VLAN_RANGES=
507
508# Comma-separated list of <tun_min>:<tun_max> tuples enumerating
509# ranges of GRE tunnel IDs that are available for tenant-network
510# allocation. A tuple must be an array with tun_max +1 - tun_min >
511# 1000000.
512CONFIG_NEUTRON_ML2_TUNNEL_ID_RANGES=
513
514# Comma-separated list of addresses for VXLAN multicast group. If
515# left empty, disables VXLAN from sending allocate broadcast traffic
516# (disables multicast VXLAN mode). Should be a Multicast IP (v4 or v6)
517# address.
518CONFIG_NEUTRON_ML2_VXLAN_GROUP=
519
520# Comma-separated list of <vni_min>:<vni_max> tuples enumerating
521# ranges of VXLAN VNI IDs that are available for tenant network
522# allocation. Minimum value is 0 and maximum value is 16777215.
523CONFIG_NEUTRON_ML2_VNI_RANGES=10:100
524
525# Name of the L2 agent to be used with OpenStack Networking.
526# ['linuxbridge', 'openvswitch', 'ovn']
527CONFIG_NEUTRON_L2_AGENT=openvswitch
528
529# Comma separated list of supported PCI vendor devices defined by
530# vendor_id:product_id according to the PCI ID Repository.
531CONFIG_NEUTRON_ML2_SUPPORTED_PCI_VENDOR_DEVS=['15b3:1004', '8086:10ca']
532
533# Comma-separated list of interface mappings for the OpenStack
534# Networking ML2 SRIOV agent. Each tuple in the list must be in the
535# format <physical_network>:<net_interface>. Example:
536# physnet1:eth1,physnet2:eth2,physnet3:eth3.
537CONFIG_NEUTRON_ML2_SRIOV_INTERFACE_MAPPINGS=
538
539# Comma-separated list of interface mappings for the OpenStack
540# Networking linuxbridge plugin. Each tuple in the list must be in the
541# format <physical_network>:<net_interface>. Example:
542# physnet1:eth1,physnet2:eth2,physnet3:eth3.
543CONFIG_NEUTRON_LB_INTERFACE_MAPPINGS=
544
545# Comma-separated list of bridge mappings for the OpenStack
546# Networking Open vSwitch plugin. Each tuple in the list must be in
547# the format <physical_network>:<ovs_bridge>. Example: physnet1:br-
548# eth1,physnet2:br-eth2,physnet3:br-eth3
549CONFIG_NEUTRON_OVS_BRIDGE_MAPPINGS=extnet:br-ex
550
551# Comma-separated list of colon-separated Open vSwitch
552# <bridge>:<interface> pairs. The interface will be added to the
553# associated bridge. If you desire the bridge to be persistent a value
554# must be added to this directive, also
555# CONFIG_NEUTRON_OVS_BRIDGE_MAPPINGS must be set in order to create
556# the proper port. This can be achieved from the command line by
557# issuing the following command: packstack --allinone --os-neutron-
558# ovs-bridge-mappings=ext-net:br-ex --os-neutron-ovs-bridge-interfaces
559# =br-ex:eth0
560CONFIG_NEUTRON_OVS_BRIDGE_IFACES=br-ex:enp4s0
561
562# Comma-separated list of Open vSwitch bridges that must be created
563# and connected to interfaces in compute nodes when flat or vlan type
564# drivers are enabled. These bridges must exist in
565# CONFIG_NEUTRON_OVS_BRIDGE_MAPPINGS and
566# CONFIG_NEUTRON_OVS_BRIDGE_IFACES. Example: --os-neutron-ovs-bridges-
567# compute=br-vlan --os-neutron-ovs-bridge-mappings="extnet:br-
568# ex,physnet1:br-vlan" --os-neutron-ovs-bridge-interfaces="br-ex:eth1
569# ,br-vlan:eth2"
570CONFIG_NEUTRON_OVS_BRIDGES_COMPUTE=br-ex
571
572# Name of physical network used for external network when enabling
573# CONFIG_PROVISION_DEMO. Name must be one of the included in
574# CONFIG_NEUTRON_OVS_BRIDGE_MAPPINGS. Example: --os-neutron-ovs-
575# bridge-mappings="extnet:br-ex,physnet1:br-vlan" --os-neutron-ovs-
576# bridge-interfaces="br-ex:eth1,br-vlan:eth2" --os-neutron-ovs-
577# external-physnet="extnet"
578CONFIG_NEUTRON_OVS_EXTERNAL_PHYSNET=extnet
579
580# Interface for the Open vSwitch tunnel. Packstack overrides the IP
581# address used for tunnels on this hypervisor to the IP found on the
582# specified interface (for example, eth1).
583CONFIG_NEUTRON_OVS_TUNNEL_IF=
584
585# Comma-separated list of subnets (for example,
586# 192.168.10.0/24,192.168.11.0/24) used for sending tunneling packets.
587# This is used to configure IP filtering to accept tunneling packets
588# from these subnets instead of specific IP addresses of peer nodes.
589# This is useful when you add existing nodes to EXCLUDE_SERVERS
590# because, in this case, packstack cannot modify the IP filtering of
591# the existing nodes.
592CONFIG_NEUTRON_OVS_TUNNEL_SUBNETS=
593
594# VXLAN UDP port.
595CONFIG_NEUTRON_OVS_VXLAN_UDP_PORT=4789
596
597# Comma-separated list of bridge mappings for the OpenStack
598# Networking Open Virtual Network plugin. Each tuple in the list must
599# be in the format <physical_network>:<ovs_bridge>. Example: physnet1
600# :br-eth1,physnet2:br-eth2,physnet3:br-eth3
601CONFIG_NEUTRON_OVN_BRIDGE_MAPPINGS=extnet:br-ex
602
603# Comma-separated list of colon-separated Open vSwitch
604# <bridge>:<interface> pairs. The interface will be added to the
605# associated bridge. If you desire the bridge to be persistent a value
606# must be added to this directive, also
607# CONFIG_NEUTRON_OVN_BRIDGE_MAPPINGS must be set in order to create
608# the proper port. This can be achieved from the command line by
609# issuing the following command: packstack --allinone --os-neutron-
610# ovn-bridge-mappings=ext-net:br-ex --os-neutron-ovn-bridge-interfaces
611# =br-ex:eth0
612CONFIG_NEUTRON_OVN_BRIDGE_IFACES=
613
614# Comma-separated list of Open vSwitch bridges that must be created
615# and connected to interfaces in compute nodes when flat or vlan type
616# drivers are enabled. These bridges must exist in
617# CONFIG_NEUTRON_OVN_BRIDGE_MAPPINGS and
618# CONFIG_NEUTRON_OVN_BRIDGE_IFACES. Example: --os-neutron-ovn-bridges-
619# compute=br-vlan --os-neutron-ovn-bridge-mappings="extnet:br-
620# ex,physnet1:br-vlan" --os-neutron-ovn-bridge-interfaces="br-ex:eth1
621# ,br-vlan:eth2"
622CONFIG_NEUTRON_OVN_BRIDGES_COMPUTE=
623
624# Name of physical network used for external network when enabling
625# CONFIG_PROVISION_DEMO. Name must be one of the included in
626# CONFIG_NEUTRON_OVN_BRIDGE_MAPPINGS. Example: --os-neutron-ovn-
627# bridge-mappings="extnet:br-ex,physnet1:br-vlan" --os-neutron-ovn-
628# bridge-interfaces="br-ex:eth1,br-vlan:eth2" --os-neutron-ovn-
629# external-physnet="extnet"
630CONFIG_NEUTRON_OVN_EXTERNAL_PHYSNET=extnet
631
632# Interface for the Open vSwitch tunnel. Packstack overrides the IP
633# address used for tunnels on this hypervisor to the IP found on the
634# specified interface (for example, eth1).
635CONFIG_NEUTRON_OVN_TUNNEL_IF=
636
637# Comma-separated list of subnets (for example,
638# 192.168.10.0/24,192.168.11.0/24) used for sending tunneling packets.
639# This is used to configure IP filtering to accept tunneling packets
640# from these subnets instead of specific IP addresses of peer nodes.
641# This is useful when you add existing nodes to EXCLUDE_SERVERS
642# because, in this case, packstack cannot modify the IP filtering of
643# the existing nodes.
644CONFIG_NEUTRON_OVN_TUNNEL_SUBNETS=
645
646# Password to use for the OpenStack File Share service (manila) to
647# access the database.
648CONFIG_MANILA_DB_PW=PW_PLACEHOLDER
649
650# Password to use for the OpenStack File Share service (manila) to
651# authenticate with the Identity service.
652CONFIG_MANILA_KS_PW=PW_PLACEHOLDER
653
654# Backend for the OpenStack File Share service (manila); valid
655# options are: generic, netapp, glusternative, or glusternfs.
656# ['generic', 'netapp', 'glusternative', 'glusternfs']
657CONFIG_MANILA_BACKEND=generic
658
659# Denotes whether the driver should handle the responsibility of
660# managing share servers. This must be set to false if the driver is
661# to operate without managing share servers. Defaults to 'false'
662# ['true', 'false']
663CONFIG_MANILA_NETAPP_DRV_HANDLES_SHARE_SERVERS=false
664
665# The transport protocol used when communicating with the storage
666# system or proxy server. Valid values are 'http' and 'https'.
667# Defaults to 'https'. ['https', 'http']
668CONFIG_MANILA_NETAPP_TRANSPORT_TYPE=https
669
670# Administrative user account name used to access the NetApp storage
671# system.  Defaults to ''.
672CONFIG_MANILA_NETAPP_LOGIN=admin
673
674# Password for the NetApp administrative user account specified in
675# the CONFIG_MANILA_NETAPP_LOGIN parameter. Defaults to ''.
676CONFIG_MANILA_NETAPP_PASSWORD=
677
678# Hostname (or IP address) for the NetApp storage system or proxy
679# server. Defaults to ''.
680CONFIG_MANILA_NETAPP_SERVER_HOSTNAME=
681
682# The storage family type used on the storage system; valid values
683# are ontap_cluster for clustered Data ONTAP. Defaults to
684# 'ontap_cluster'. ['ontap_cluster']
685CONFIG_MANILA_NETAPP_STORAGE_FAMILY=ontap_cluster
686
687# The TCP port to use for communication with the storage system or
688# proxy server. If not specified, Data ONTAP drivers will use 80 for
689# HTTP and 443 for HTTPS. Defaults to '443'.
690CONFIG_MANILA_NETAPP_SERVER_PORT=443
691
692# Pattern for searching available aggregates for NetApp provisioning.
693# Defaults to '(.*)'.
694CONFIG_MANILA_NETAPP_AGGREGATE_NAME_SEARCH_PATTERN=(.*)
695
696# Name of aggregate on which to create the NetApp root volume. This
697# option only applies when the option
698# CONFIG_MANILA_NETAPP_DRV_HANDLES_SHARE_SERVERS is set to True.
699CONFIG_MANILA_NETAPP_ROOT_VOLUME_AGGREGATE=
700
701# NetApp root volume name. Defaults to 'root'.
702CONFIG_MANILA_NETAPP_ROOT_VOLUME_NAME=root
703
704# This option specifies the storage virtual machine (previously
705# called a Vserver) name on the storage cluster on which provisioning
706# of shared file systems should occur. This option only applies when
707# the option driver_handles_share_servers is set to False. Defaults to
708# ''.
709CONFIG_MANILA_NETAPP_VSERVER=
710
711# Denotes whether the driver should handle the responsibility of
712# managing share servers. This must be set to false if the driver is
713# to operate without managing share servers. Defaults to 'true'.
714# ['true', 'false']
715CONFIG_MANILA_GENERIC_DRV_HANDLES_SHARE_SERVERS=true
716
717# Volume name template for Manila service. Defaults to 'manila-
718# share-%s'.
719CONFIG_MANILA_GENERIC_VOLUME_NAME_TEMPLATE=manila-share-%s
720
721# Share mount path for Manila service. Defaults to '/shares'.
722CONFIG_MANILA_GENERIC_SHARE_MOUNT_PATH=/shares
723
724# Location of disk image for Manila service instance. Defaults to '
725CONFIG_MANILA_SERVICE_IMAGE_LOCATION=https://www.dropbox.com/s/vi5oeh10q1qkckh/ubuntu_1204_nfs_cifs.qcow2
726
727# User in Manila service instance.
728CONFIG_MANILA_SERVICE_INSTANCE_USER=ubuntu
729
730# Password to service instance user.
731CONFIG_MANILA_SERVICE_INSTANCE_PASSWORD=ubuntu
732
733# Type of networking that the backend will use. A more detailed
734# description of each option is available in the Manila docs. Defaults
735# to 'neutron'. ['neutron', 'nova-network', 'standalone']
736CONFIG_MANILA_NETWORK_TYPE=neutron
737
738# Gateway IPv4 address that should be used. Required. Defaults to ''.
739CONFIG_MANILA_NETWORK_STANDALONE_GATEWAY=
740
741# Network mask that will be used. Can be either decimal like '24' or
742# binary like '255.255.255.0'. Required. Defaults to ''.
743CONFIG_MANILA_NETWORK_STANDALONE_NETMASK=
744
745# Set it if network has segmentation (VLAN, VXLAN, etc). It will be
746# assigned to share-network and share drivers will be able to use this
747# for network interfaces within provisioned share servers. Optional.
748# Example: 1001. Defaults to ''.
749CONFIG_MANILA_NETWORK_STANDALONE_SEG_ID=
750
751# Can be IP address, range of IP addresses or list of addresses or
752# ranges. Contains addresses from IP network that are allowed to be
753# used. If empty, then will be assumed that all host addresses from
754# network can be used. Optional. Examples: 10.0.0.10 or
755# 10.0.0.10-10.0.0.20 or
756# 10.0.0.10-10.0.0.20,10.0.0.30-10.0.0.40,10.0.0.50. Defaults to ''.
757CONFIG_MANILA_NETWORK_STANDALONE_IP_RANGE=
758
759# IP version of network. Optional. Defaults to '4'. ['4', '6']
760CONFIG_MANILA_NETWORK_STANDALONE_IP_VERSION=4
761
762# List of GlusterFS servers that can be used to create shares. Each
763# GlusterFS server should be of the form [remoteuser@]<volserver>, and
764# they are assumed to belong to distinct Gluster clusters.
765CONFIG_MANILA_GLUSTERFS_SERVERS=
766
767# Path of Manila host's private SSH key file.
768CONFIG_MANILA_GLUSTERFS_NATIVE_PATH_TO_PRIVATE_KEY=
769
770# Regular expression template used to filter GlusterFS volumes for
771# share creation. The regex template can optionally (ie. with support
772# of the GlusterFS backend) contain the #{size} parameter which
773# matches an integer (sequence of digits) in which case the value
774# shall be intepreted as size of the volume in GB. Examples: "manila-
775# share-volume-d+$", "manila-share-volume-#{size}G-d+$"; with matching
776# volume names, respectively: "manila-share-volume-12", "manila-share-
777# volume-3G-13". In latter example, the number that matches "#{size}",
778# that is, 3, is an indication that the size of volume is 3G.
779CONFIG_MANILA_GLUSTERFS_VOLUME_PATTERN=
780
781# Specifies the GlusterFS volume to be mounted on the Manila host.
782# For e.g: [remoteuser@]<volserver>:/<volid>
783CONFIG_MANILA_GLUSTERFS_TARGET=
784
785# Base directory containing mount points for Gluster volumes.
786CONFIG_MANILA_GLUSTERFS_MOUNT_POINT_BASE=
787
788# Type of NFS server that mediate access to the Gluster volumes
789# (Gluster or Ganesha).
790CONFIG_MANILA_GLUSTERFS_NFS_SERVER_TYPE=gluster
791
792# Path of Manila host's private SSH key file.
793CONFIG_MANILA_GLUSTERFS_PATH_TO_PRIVATE_KEY=
794
795# Remote Ganesha server node's IP address.
796CONFIG_MANILA_GLUSTERFS_GANESHA_SERVER_IP=
797
798# Specify 'y' to set up Horizon communication over https. ['y', 'n']
799CONFIG_HORIZON_SSL=n
800
801# Secret key to use for Horizon Secret Encryption Key.
802CONFIG_HORIZON_SECRET_KEY=402e67793cc5428b9a53610db4cd194c
803
804# PEM-encoded certificate to be used for SSL connections on the https
805# server. To generate a certificate, leave blank.
806CONFIG_HORIZON_SSL_CERT=
807
808# SSL keyfile corresponding to the certificate if one was specified.
809# The certificate should not require a passphrase.
810CONFIG_HORIZON_SSL_KEY=
811
812CONFIG_HORIZON_SSL_CACERT=
813
814# Password to use for the Object Storage service to authenticate with
815# the Identity service.
816CONFIG_SWIFT_KS_PW=57c122fc81b244e0
817
818# Comma-separated list of devices to use as storage device for Object
819# Storage. Each entry must take the format /path/to/dev (for example,
820# specifying /dev/vdb installs /dev/vdb as the Object Storage storage
821# device; Packstack does not create the filesystem, you must do this
822# first). If left empty, Packstack creates a loopback device for test
823# setup.
824CONFIG_SWIFT_STORAGES=/dev/sdb2,/dev/sdb3,/dev/sdb4
825
826# Number of Object Storage storage zones; this number MUST be no
827# larger than the number of configured storage devices.
828CONFIG_SWIFT_STORAGE_ZONES=1
829
830# Number of Object Storage storage replicas; this number MUST be no
831# larger than the number of configured storage zones.
832CONFIG_SWIFT_STORAGE_REPLICAS=2
833
834# File system type for storage nodes. ['xfs', 'ext4']
835CONFIG_SWIFT_STORAGE_FSTYPE=xfs
836
837# Custom seed number to use for swift_hash_path_suffix in
838# /etc/swift/swift.conf. If you do not provide a value, a seed number
839# is automatically generated.
840CONFIG_SWIFT_HASH=c9ead3a56b8a429c
841
842# Size of the Object Storage loopback file storage device.
843CONFIG_SWIFT_STORAGE_SIZE=2G
844
845# Password used by Orchestration service user to authenticate against
846# the database.
847CONFIG_HEAT_DB_PW=PW_PLACEHOLDER
848
849# Encryption key to use for authentication in the Orchestration
850# database (16, 24, or 32 chars).
851CONFIG_HEAT_AUTH_ENC_KEY=ad1eb8c2d4b141a5
852
853# Password to use for the Orchestration service to authenticate with
854# the Identity service.
855CONFIG_HEAT_KS_PW=PW_PLACEHOLDER
856
857# Specify 'y' to install the Orchestration CloudFormation API. ['y',
858# 'n']
859CONFIG_HEAT_CFN_INSTALL=y
860
861# Name of the Identity domain for Orchestration.
862CONFIG_HEAT_DOMAIN=heat
863
864# Name of the Identity domain administrative user for Orchestration.
865CONFIG_HEAT_DOMAIN_ADMIN=heat_admin
866
867# Password for the Identity domain administrative user for
868# Orchestration.
869CONFIG_HEAT_DOMAIN_PASSWORD=PW_PLACEHOLDER
870
871# Specify 'y' to provision for demo usage and testing. ['y', 'n']
872CONFIG_PROVISION_DEMO=n
873
874# Specify 'y' to configure the OpenStack Integration Test Suite
875# (tempest) for testing. The test suite requires OpenStack Networking
876# to be installed. ['y', 'n']
877CONFIG_PROVISION_TEMPEST=n
878
879# CIDR network address for the floating IP subnet.
880CONFIG_PROVISION_DEMO_FLOATRANGE=172.24.4.0/24
881
882# Allocation pools in the floating IP subnet.
883CONFIG_PROVISION_DEMO_ALLOCATION_POOLS=[]
884
885# The name to be assigned to the demo image in Glance (default
886# "cirros").
887CONFIG_PROVISION_IMAGE_NAME=cirros
888
889# A URL or local file location for an image to download and provision
890# in Glance (defaults to a URL for a recent "cirros" image).
891CONFIG_PROVISION_IMAGE_URL=http://download.cirros-cloud.net/0.3.5/cirros-0.3.5-x86_64-disk.img
892
893# Format for the demo image (default "qcow2").
894CONFIG_PROVISION_IMAGE_FORMAT=qcow2
895
896# Properties of the demo image (none by default).
897CONFIG_PROVISION_IMAGE_PROPERTIES=
898
899# User to use when connecting to instances booted from the demo
900# image.
901CONFIG_PROVISION_IMAGE_SSH_USER=cirros
902
903# Name of the uec image created in Glance used in tempest tests
904# (default "cirros-uec").
905CONFIG_PROVISION_UEC_IMAGE_NAME=cirros-uec
906
907# URL of the kernel image copied to Glance image for uec image
908# (defaults to a URL for a recent "cirros" uec image).
909CONFIG_PROVISION_UEC_IMAGE_KERNEL_URL=http://download.cirros-cloud.net/0.3.5/cirros-0.3.5-x86_64-kernel
910
911# URL of the ramdisk image copied to Glance image for uec image
912# (defaults to a URL for a recent "cirros" uec image).
913CONFIG_PROVISION_UEC_IMAGE_RAMDISK_URL=http://download.cirros-cloud.net/0.3.5/cirros-0.3.5-x86_64-initramfs
914
915# URL of the disk image copied to Glance image for uec image
916# (defaults to a URL for a recent "cirros" uec image).
917CONFIG_PROVISION_UEC_IMAGE_DISK_URL=http://download.cirros-cloud.net/0.3.5/cirros-0.3.5-x86_64-disk.img
918
919CONFIG_TEMPEST_HOST=
920
921# Name of the Integration Test Suite provisioning user. If you do not
922# provide a user name, Tempest is configured in a standalone mode.
923CONFIG_PROVISION_TEMPEST_USER=
924
925# Password to use for the Integration Test Suite provisioning user.
926CONFIG_PROVISION_TEMPEST_USER_PW=PW_PLACEHOLDER
927
928# CIDR network address for the floating IP subnet.
929CONFIG_PROVISION_TEMPEST_FLOATRANGE=172.24.4.0/24
930
931# Primary flavor name to use in Tempest.
932CONFIG_PROVISION_TEMPEST_FLAVOR_NAME=m1.nano
933
934# Primary flavor's disk quota in Gb.
935CONFIG_PROVISION_TEMPEST_FLAVOR_DISK=0
936
937# Primary flavor's ram in Mb.
938CONFIG_PROVISION_TEMPEST_FLAVOR_RAM=128
939
940# Primary flavor's vcpus number.
941CONFIG_PROVISION_TEMPEST_FLAVOR_VCPUS=1
942
943# Alternative flavor name to use in Tempest.
944CONFIG_PROVISION_TEMPEST_FLAVOR_ALT_NAME=m1.micro
945
946# Alternative flavor's disk quota in Gb.
947CONFIG_PROVISION_TEMPEST_FLAVOR_ALT_DISK=0
948
949# Alternative flavor's ram in Mb.
950CONFIG_PROVISION_TEMPEST_FLAVOR_ALT_RAM=128
951
952# Alternative flavor's vcpus number.
953CONFIG_PROVISION_TEMPEST_FLAVOR_ALT_VCPUS=1
954
955# Specify 'y' to run Tempest smoke test as last step of installation.
956CONFIG_RUN_TEMPEST=n
957
958# Test suites to run, example: "smoke dashboard TelemetryAlarming".
959# Optional, defaults to "smoke".
960CONFIG_RUN_TEMPEST_TESTS=smoke
961
962# Specify 'y' to configure the Open vSwitch external bridge for an
963# all-in-one deployment (the L3 external bridge acts as the gateway
964# for virtual machines). ['y', 'n']
965CONFIG_PROVISION_OVS_BRIDGE=y
966
967# Password to use for Gnocchi to access the database.
968CONFIG_GNOCCHI_DB_PW=PW_PLACEHOLDER
969
970# Password to use for Gnocchi to authenticate with the Identity
971# service.
972CONFIG_GNOCCHI_KS_PW=PW_PLACEHOLDER
973
974# Secret key for signing Telemetry service (ceilometer) messages.
975CONFIG_CEILOMETER_SECRET=b431b4a8b6a1412d
976
977# Password to use for Telemetry to authenticate with the Identity
978# service.
979CONFIG_CEILOMETER_KS_PW=PW_PLACEHOLDER
980
981# Ceilometer service name. ['httpd', 'ceilometer']
982CONFIG_CEILOMETER_SERVICE_NAME=httpd
983
984# Backend driver for Telemetry's group membership coordination.
985# ['redis', 'none']
986CONFIG_CEILOMETER_COORDINATION_BACKEND=redis
987
988# Whether to enable ceilometer middleware in swift proxy. By default
989# this should be false to avoid unnecessary load.
990CONFIG_ENABLE_CEILOMETER_MIDDLEWARE=n
991
992# IP address of the server on which to install the Redis server.
993CONFIG_REDIS_HOST=10.1.1.2
994
995# Port on which the Redis server listens.
996CONFIG_REDIS_PORT=6379
997
998# Password to use for Telemetry Alarming to authenticate with the
999# Identity service.
1000CONFIG_AODH_KS_PW=PW_PLACEHOLDER
1001
1002# Password to use for Telemetry Alarming (AODH) to access the
1003# database.
1004CONFIG_AODH_DB_PW=PW_PLACEHOLDER
1005
1006# Password to use for Panko to access the database.
1007CONFIG_PANKO_DB_PW=PW_PLACEHOLDER
1008
1009# Password to use for Panko to authenticate with the Identity
1010# service.
1011CONFIG_PANKO_KS_PW=PW_PLACEHOLDER
1012
1013# Password to use for OpenStack Database-as-a-Service (trove) to
1014# access the database.
1015CONFIG_TROVE_DB_PW=PW_PLACEHOLDER
1016
1017# Password to use for OpenStack Database-as-a-Service to authenticate
1018# with the Identity service.
1019CONFIG_TROVE_KS_PW=PW_PLACEHOLDER
1020
1021# User name to use when OpenStack Database-as-a-Service connects to
1022# the Compute service.
1023CONFIG_TROVE_NOVA_USER=trove
1024
1025# Tenant to use when OpenStack Database-as-a-Service connects to the
1026# Compute service.
1027CONFIG_TROVE_NOVA_TENANT=services
1028
1029# Password to use when OpenStack Database-as-a-Service connects to
1030# the Compute service.
1031CONFIG_TROVE_NOVA_PW=PW_PLACEHOLDER
1032
1033# Password to use for OpenStack Data Processing (sahara) to access
1034# the database.
1035CONFIG_SAHARA_DB_PW=PW_PLACEHOLDER
1036
1037# Password to use for OpenStack Data Processing to authenticate with
1038# the Identity service.
1039CONFIG_SAHARA_KS_PW=PW_PLACEHOLDER
1040
1041# Password to use for the Magnum to access the database.
1042CONFIG_MAGNUM_DB_PW=PW_PLACEHOLDER
1043
1044# Password to use for the Magnum to authenticate with the Identity
1045# service.
1046CONFIG_MAGNUM_KS_PW=PW_PLACEHOLDER