Appendix A. Answer File Configuration Keys

You can edit Packstack answer files in any text editor; lines preceded with a # character are ignored.

Note

For command-line equivalents, see the "Command-Line Interface Reference"- https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/.
The following table provides available configuration keys; specify configuration values using the syntax: KEY=VALUE. Keys are listed in the order they appear in the default answer file.

Table A.1. Answer file configuration keys

Key Default Value Description
CONFIG_SSH_KEY /root/.ssh/id_rsa.pub Path to a public key to install on servers. If a usable key has not been installed on the remote servers, you will be prompted for a password and this key will be installed so the password will not be required again.
CONFIG_DEFAULT_PASSWORD  Default password to be used everywhere (overridden by passwords set for individual services or users).
CONFIG_MARIADB_INSTALL y
Specify y to have Packstack install MariaDB.
If you specify n, Packstack asks you for credentials and uses CONFIG_MARIADB_HOST as the database.
Packstack is only capable of installing a single MariaDB database node. Although Packstack does not handle MariaDB cluster installation, it does allow you to work with a MariaDB cluster that you have set up separately.
CONFIG_GLANCE_INSTALL y Specify y if you would like Packstack to install the Image service.
CONFIG_CINDER_INSTALL y Specify y if you would like Packstack to install the Volume service.
CONFIG_NOVA_INSTALL y Specify y if you would like Packstack to install the Compute service.
CONFIG_NEUTRON_INSTALL y Specify y if you would like Packstack to install the OpenStack Networking service.
CONFIG_HORIZON_INSTALL y Specify y if you would like Packstack to install the dashboard service.
CONFIG_SWIFT_INSTALL y Specify y if you would like Packstack to install the Object Storage service.
CONFIG_CEILOMETER_INSTALL y Specify y if you would like Packstack to install the Telemetry service.
CONFIG_HEAT_INSTALL n Specify y if you would like Packstack to install the Orchestration service.
CONFIG_CLIENT_INSTALL y Specify y if you would like Packstack to install the OpenStack client packages (command-line tools). An admin "rc" file will also be installed.
CONFIG_NTP_SERVERS  Comma-separated list of NTP servers. Leave empty if Packstack should not install NTPD on instances.
CONFIG_NAGIOS_INSTALL y Specify y if you would like to install Nagios. Nagios provides additional tools for monitoring the OpenStack environment.
EXCLUDE_SERVERS  
Comma-separated list of servers to be excluded from configuration. This is helpful if you have existing servers that have been configured previously (for example, you have already run packstack), and you do not want Packstack to overwrite their configurations.
Leave empty if you do not need to exclude any servers.
CONFIG_DEBUG_MODE n Specify y if you want to run OpenStack services in debug mode; otherwise, leave the n default.
CONFIG_CONTROLLER_HOST HOST IP IP address of the server on which to install OpenStack services specific to the controller role (for example, API servers, Object Storage, or the dashboard).
CONFIG_COMPUTE_HOSTS HOST IP List of IP addresses of the servers on which to install the Compute service.
CONFIG_NETWORK_HOSTS HOST IP List of IP addresses of the servers on which to install the networking service (OpenStack Networking (neutron) or Compute networking (nova-networking)). Networking API and LBAAS services will still be installed on the controller host.
CONFIG_VMWARE_BACKEND n Set to y if you want to use the VMware vCenter as hypervisor and storage; otherwise, leave the n default.
CONFIG_UNSUPPORTED n Enables the use of unsupported parameters. Currently only for development; only use if you know what you are doing.
CONFIG_VCENTER_HOST  IP address of the VMware vCenter server.
CONFIG_VCENTER_USER User name for VMware vCenter server authentication.
CONFIG_VCENTER_PASSWORD Password for VMware vCenter server authentication.
CONFIG_VCENTER_CLUSTER_NAME The name of the VMware vCenter cluster.
CONFIG_USE_EPEL n To subscribe each server to the EPEL upstream repository (Extra Packages for Enterprise Linux), specify y.
CONFIG_REPO  A comma-separated list of URLs to any additional yum repositories, to use for installation.
CONFIG_RH_USER  To subscribe each server with Red Hat Subscription Manager, include this with CONFIG_RH_PW.
CONFIG_RH_PW  To subscribe each server with Red Hat Subscription Manager, include this with CONFIG_RH_USER.
CONFIG_RH_OPTIONAL y To enable Red Hat Enterprise Linux optional repositories, specify y.
CONFIG_RH_PROXY  HTTP proxy to use with Red Hat subscription manager.
CONFIG_RH_PROXY_PORT  Port to use for Red Hat subscription manager's HTTP proxy.
CONFIG_RH_PROXY_USER  User to use for Red Hat subscription manager's HTTP proxy.
CONFIG_RH_PROXY_PW  Password to use for Red Hat subscription manager's HTTP proxy.
CONFIG_SATELLITE_URL  To subscribe each server to receive updates from a Satellite server, provide the URL of the Satellite server. You must also provide a user name (CONFIG_SATELLITE_USERNAME) and password (CONFIG_SATELLITE_PASSWORD) or an access key (CONFIG_SATELLITE_AKEY) for authentication.
CONFIG_SATELLITE_USER  
User name for the Satellite server; if you intend to use an access key for Satellite authentication, leave this configuration key blank.
CONFIG_SATELLITE_PW  
Password for the Satellite server; if you intend to use an access key for Satellite authentication, leave this configuration key blank.
CONFIG_SATELLITE_AKEY  
Access key for the Satellite server; if you intend to use a user name and password for Satellite authentication, leave this configuration key blank.
CONFIG_SATELLITE_CACERT  
Certificate path of the certificate authority to verify that the connection with the Satellite server is secure. Leave blank if you are not using Satellite in your deployment.
CONFIG_SATELLITE_PROFILE  
Profile name to use as an identifier in the Satellite system, if required.
CONFIG_SATELLITE_FLAGS  
Additional Satellite flags to be passed to the rhnreg_ks command. This configuration key accepts a comma-separated list of flags. Valid flags are novirtinfo, norhnsd, and nopackages.
See the Red Hat Satellite documentation for more information.
CONFIG_SATELLITE_PROXY  
HTTP proxy to use when connecting to the Satellite server, if required.
CONFIG_SATELLITE_PROXY_USER  
User name to authenticate with the HTTP proxy that must be used when connecting to the Satellite server, if required.
CONFIG_SATELLITE_PROXY_PW  
Password to authenticate with the HTTP proxy server that must be used when connecting to the Satellite server, if required.
CONFIG_AMQP_BACKEND rabbitmq AMQP service (broker) to use as the backend. Supported values are: qpid or rabbitmq.
CONFIG_AMQP_HOST HOST IP IP address of the server on which to install the AMQP service.
CONFIG_AMQP_ENABLE_SSL n Specify y to enable SSL for the AMQP service.
CONFIG_AMQP_ENABLE_AUTH n Specify y to enable authentication for the AMQP service.
CONFIG_AMQP_NSS_CERTDB_PW Password for the NSS certificate database of the AMQP service.
CONFIG_AMQP_SSL_PORT 5671 Port on which the AMQP service listens for SSL connections.
CONFIG_AMQP_SSL_CERT_FILE /etc/pki/tls/certs/amqp_selfcert.pem File name of the certificate that the AMQP service is going to use.
CONFIG_AMQP_SSL_KEY_FILE /etc/pki/tls/private/amqp_selfkey.pem File name of the private key that the AMQP service is going to use.
CONFIG_AMQP_SSL_SELF_SIGNED y Specify y to automatically generate an SSL certificate and key.
CONFIG_AMQP_AUTH_USER amqp_user User for AMQP authentication.
CONFIG_AMQP_AUTH_PASSWORD Password for AMQP authentication.
CONFIG_MARIADB_HOST HOST IP IP address of the server on which to install MariaDB or, alternatively, the IP address of the DB server to use if MariaDB installation was not selected.
CONFIG_MARIADB_USER root User name for the MariaDB administrative user.
CONFIG_MARIADB_PW Randomly generatedPassword for the MariaDB administrative user.
CONFIG_KEYSTONE_DB_PW Randomly generatedPassword to use for Identity to access the database.
CONFIG_KEYSTONE_REGION RegionOne Default region to use when creating tenants in the Identity service.
CONFIG_KEYSTONE_ADMIN_TOKEN Randomly generatedToken to use for the Identity service API.
CONFIG_KEYSTONE_ADMIN_PW Randomly generatedPassword to use for the Identity administrative user.
CONFIG_KEYSTONE_DEMO_PW Randomly generatedPassword to use for the demo tenant. Only used if CONFIG_PROVISION_DEMO=y
CONFIG_KEYSTONE_TOKEN_FORMAT UUID Packstack allows a choice of the token format to be used by the Identity service. Supported values are: PKI or UUID. The recommended format for new deployments is UUID.
CONFIG_KEYSTONE_SERVICE_NAME keystone Name of service to use to run the Identity service. Supported values are: keystone or httpd.
CONFIG_GLANCE_DB_PW Randomly generatedPassword to use for the Image service to access its database.
CONFIG_GLANCE_KS_PW Randomly generatedPassword to use for the Image service to authenticate with the Identity service.
CONFIG_GLANCE_BACKEND file Controls how the Image service stores disk images. Supported values are: file or swift. The Object Storage service (swift) must be enabled to use it as a working backend; otherwise, Packstack falls back to 'file'.
CONFIG_CINDER_DB_PW Randomly generatedPassword to use for the Block Storage service to access its database.
CONFIG_CINDER_KS_PW Randomly generatedThe password to use for the Block Storage service to authenticate with the Identity service.
CONFIG_CINDER_BACKEND lvm Backend to use for the Block Storage service. Supported values are: lvm, gluster, nfs.
CONFIG_CINDER_VOLUMES_CREATE y
Packstack expects storage for use with the Block Storage service to be available on a volume group named cinder-volumes. If y is specified and this volume group does not already exist, Packstack creates it. That is, Packstack creates a raw disk image in the /var/lib/cinder and mounts it for use by the Block Storage service using a loopback device.
This should only be used for testing on a proof-of-concept installation of the Block Storage service (a file-backed volume group is not suitable for production usage).
CONFIG_CINDER_VOLUMES_SIZE 20G
If you elected to have Packstack create the cinder-volumes volume group (CONFIG_CINDER_VOLUMES_CREATE=y), you must to provide its desired size in gigabytes (GB). Actual volume size will be extended with 3% more space for VG metadata.

Important

  • Remember that the size of the volume group will restrict the amount of disk space that you can expose to Compute instances.
  • The amount of space selected for CONFIG_CINDER_VOLUMES_SIZE must be available on the device used for /var/lib/cinder.
CONFIG_CINDER_GLUSTER_MOUNTS  
A single or comma-separated list of gluster volume shares to mount. Example: ip-address:/vol-name, domain:/vol-name
CONFIG_CINDER_NFS_MOUNTS
A single or comma-separated list of NFS exports to mount. Example: ip-address:/export-name
CONFIG_CINDER_NETAPP_LOGIN  Administrative user account name used to access the storage system or proxy server. Required.
CONFIG_CINDER_NETAPP_PASSWORD  Password for the administrative user account specified in the CONFIG_CINDER_NETAPP_LOGIN parameter. Required.
CONFIG_CINDER_NETAPP_HOSTNAME  Hostname (or IP address) for the storage system or proxy server. Required.
CONFIG_CINDER_NETAPP_SERVER_PORT 80 TCP port to use for communication with ONTAPI on the storage system. Traditionally, port 80 is used for HTTP and port 443 is used for HTTPS. However, this value should be changed if an alternate port has been configured on the storage system or proxy server. Optional.
CONFIG_CINDER_NETAPP_STORAGE_FAMILY ontap_cluster
The storage family type used on the storage system (optional); supported values are:
  • ontap_7mode - Using Data ONTAP operating in 7-Mode.
  • ontap_cluster - Using clustered Data ONTAP.
  • eseries - Using NetApp E-Series.
CONFIG_CINDER_NETAPP_TRANSPORT_TYPE http Transport protocol used when communicating with ONTAPI on the storage system or proxy server. Valid values are http or https. Optional.
CONFIG_CINDER_NETAPP_STORAGE_PROTOCOL nfs Storage protocol to be used on the data path with the storage system; supported values are: iscsi or nfs. Optional.
CONFIG_CINDER_NETAPP_SIZE_MULTIPLIER 1.0 Quantity to be multiplied by the requested volume size to ensure enough space is available on the virtual storage server (Vserver) to fulfill the volume-creation request. Optional.
CONFIG_CINDER_NETAPP_EXPIRY_THRES_MINUTES 720 Time period (in minutes) that is allowed to elapse after the image is last accessed, before it is deleted from the NFS image cache. When a cache-cleaning cycle begins, images in the cache that have not been accessed in the last M minutes, where M is the value of this parameter, are deleted from the cache to create free space on the NFS share. Optional.
CONFIG_CINDER_NETAPP_THRES_AVL_SIZE_PERC_START 20 If the percentage of available space for an NFS share has dropped below the value specified by this parameter, the NFS image cache is cleaned. Optional.
CONFIG_CINDER_NETAPP_THRES_AVL_SIZE_PERC_STOP 60 When the percentage of available space on an NFS share has reached the percentage specified by this parameter, the driver stops clearing files from the NFS image cache that have not been accessed in the last M minutes, where M is the value of the CONFIG_CINDER_NETAPP_EXPIRY_THRES_MINUTES parameter. Optional.
CONFIG_CINDER_NETAPP_NFS_SHARES_CONFIG  File with the list of available NFS shares. Optional.
CONFIG_CINDER_NETAPP_VOLUME_LIST  Restricts provisioning to the specified controller volumes; the value must be a comma-separated list of NetApp controller volume names. This parameter is only utilized when the storage protocol is configured to use iSCSI. Optional.
CONFIG_CINDER_NETAPP_VFILER  vFiler unit on which block storage volumes will be provisioned. This parameter is only used by the driver when connecting to an instance with a storage family of Data ONTAP operating in 7-Mode and the storage protocol is iSCSI. Only use this parameter when utilizing the MultiStore feature on the NetApp storage system. Optional.
CONFIG_CINDER_NETAPP_VSERVER  
Specifies the virtual storage server (Vserver) name on the storage cluster on which provisioning of Block Storage volumes should occur; the exports belonging to the Vserver are only used for provisioning in the future. Block Storage volumes on exports not belonging to the Vserver specified by this parameter will continue to function normally.
If using the NFS storage protocol, this parameter is mandatory for storage service catalog support (utilized by Block Storage volume type extra_specs support); otherwise, the parameter is optional.
CONFIG_CINDER_NETAPP_CONTROLLER_IPS  Restricts provisioning to the specified controllers. Value must be a comma-separated list of controller hostnames or IP addresses to be used for provisioning. This option is only utilized when the storage family is configured to E-Series. Optional.
CONFIG_CINDER_NETAPP_SA_PASSWORD  Password for the NetApp E-Series storage array. Optional.
CONFIG_CINDER_NETAPP_WEBSERVICE_PATH /devmgr/v2 Path to the E-Series proxy application on a proxy server. The value is combined with the value of the CONFIG_CINDER_NETAPP_TRANSPORT_TYPE, CONFIG_CINDER_NETAPP_HOSTNAME, and CONFIG_CINDER_NETAPP_HOSTNAME options to create the URL used by the driver to connect to the proxy application. Optional.
CONFIG_CINDER_NETAPP_STORAGE_POOLS  Restricts provisioning to the specified storage pools. Only dynamic disk pools are currently supported. Value is comma-separated list of disk pool names to be used for provisioning. Optional.
CONFIG_NOVA_DB_PW Randomly generatedPassword to use for Compute to access the database.
CONFIG_NOVA_KS_PW Randomly generatedPassword to use for Compute to authenticate with Identity.
CONFIG_NOVA_SCHED_CPU_ALLOC_RATIO 16.0 Overcommitment ratio for virtual to physical CPUs. Specify 1.0 to disable CPU overcommitment.
CONFIG_NOVA_SCHED_RAM_ALLOC_RATIO 1.5 Overcommitment ratio for virtual to physical RAM. Specify 1.0 to disable RAM overcommitment.
CONFIG_NOVA_COMPUTE_MIGRATE_PROTOCOL tcp Protocol used for instance migration. Supported values: tcp or ssh. Note that by default, the nova user is created with /sbin/nologin shell so that the ssh protocol will not work. To make the ssh protocol work, you must fix the nova user on compute hosts manually.
CONFIG_NOVA_COMPUTE_PRIVIF eth1 Private interface for Flat DHCP on the Compute servers.
CONFIG_NOVA_NETWORK_MANAGER nova.network.manager.FlatDHCPManager Compute Network Manager.
CONFIG_NOVA_NETWORK_PUBIF eth0 Public interface on the Compute network server.
CONFIG_NOVA_NETWORK_PRIVIF eth1 Private interface for Flat DHCP on the Compute network server.
CONFIG_NOVA_NETWORK_FIXEDRANGE HOST IP/22 IP Range for Flat DHCP.
CONFIG_NOVA_NETWORK_FLOATRANGE 10.3.4.0/22 IP Range for Floating IP addresses.
CONFIG_NOVA_NETWORK_DEFAULTFLOATINGPOOL nova Name of the default floating pool to which the specified floating ranges are added.
CONFIG_NOVA_NETWORK_AUTOASSIGNFLOATINGIP n Automatically assign a floating IP to new instances.
CONFIG_NOVA_NETWORK_VLAN_START 100 First VLAN for private networks.
CONFIG_NOVA_NETWORK_NUMBER 1 Number of networks to support.
CONFIG_NOVA_NETWORK_SIZE 255 Number of addresses in each private subnet.
CONFIG_NEUTRON_USE_NAMESPACES y Enable network namespaces for OpenStack Networking.
CONFIG_NEUTRON_KS_PW Randomly generatedThe password to use for OpenStack Networking to authenticate with Identity.
CONFIG_NEUTRON_DB_PW Randomly generatedThe password to use for OpenStack Networking to access its database.
CONFIG_NEUTRON_L3_EXT_BRIDGE br-ex The name of the bridge that the OpenStack Networking L3 agent will use for external traffic. Use provider if you intend to use a provider network to handle external traffic.
CONFIG_NEUTRON_L2_PLUGIN ml2 The name of the L2 plugin to be used with OpenStack Networking (for example, linuxbridge, openvswitch, or ml2).
CONFIG_NEUTRON_METADATA_PW Randomly generatedPassword for the OpenStack Networking metadata agent.
CONFIG_LBAAS_INSTALL n Specify y if you would like Packstack to install OpenStack Networking LBaaS.
CONFIG_NEUTRON_METERING_AGENT_INSTALL n Specify y if you would like Packstack to install OpenStack Networking Metering agent.
CONFIG_NEUTRON_FWAAS n Specify y if you would like to configure OpenStack Networking's firewall as a service.
CONFIG_NEUTRON_ML2_TYPE_DRIVERS vxlan A comma-separated list of network-type driver entry points to be loaded from the neutron.ml2.type_drivers namespace.
CONFIG_NEUTRON_ML2_TENANT_NETWORK_TYPES vxlan A comma-separated ordered list of network types to allocate as tenant networks. The value local is only useful for single-box testing but provides no connectivity between hosts.
CONFIG_NEUTRON_ML2_MECHANISM_DRIVERS openvswitch A comma-separated ordered list of networking mechanism driver entry points to be loaded from the neutron.ml2.mechanism_drivers namespace.
CONFIG_NEUTRON_ML2_FLAT_NETWORKS * A comma-separated list of physical_network names with which flat networks can be created. Use * to allow flat networks with arbitrary physical network names.
CONFIG_NEUTRON_ML2_VLAN_RANGES A comma-separated list of physical_network:vlan_min:vlan_max or physical_network specifying physical_network names usable for VLAN provider and tenant networks, as well as ranges of VLAN tags on each available for allocation to tenant networks.
CONFIG_NEUTRON_ML2_TUNNEL_ID_RANGES A comma-separated list of tun_min:tun_max tuples enumerating ranges of GRE tunnel IDs that are available for tenant network allocation. It must be an array with tun_max +1 - tun_min > 1,000,000
CONFIG_NEUTRON_ML2_VXLAN_GROUP Multicast group for VXLAN. If not set, disables VXLAN from sending allocated broadcast traffic to this multicast group. If left blank, disables multicast VXLAN mode. Must be a Multicast IP (v4 or v6) address.
CONFIG_NEUTRON_ML2_VNI_RANGES 10:100 A comma-separated list of vni_min:vni_max tuples enumerating ranges of VXLAN VNI IDs that are available for tenant network allocation. Minimum value is 0; maximum value is 16777215.
CONFIG_NEUTRON_L2_AGENT openvswitch The name of the L2 agent to be used with OpenStack Networking.
CONFIG_NEUTRON_LB_TENANT_NETWORK_TYPE local Type of network to allocate for tenant networks. Supported values are: local or vlan. For multi-node deployments, vlan is recommended.
CONFIG_NEUTRON_LB_VLAN_RANGES  A comma-separated list of VLAN ranges for the OpenStack Networking linuxbridge plugin. Each tuple in the list is expected to be in the format PHYSICAL:START:END. Replace PHYSICAL with the name of a physical network, replace START with the start of the VLAN range to identify with it, and replace END with the end of the VLAN range to associate with it. Example: physnet1:1:4094,physnet2,physnet3:3000:3999
CONFIG_NEUTRON_LB_INTERFACE_MAPPINGS  A comma-separated list of interface mappings for the OpenStack Networking linuxbridge plugin. Each tuple in the list is expected to be in the format PHYSICAL:INTERFACE. Replace PHYSICAL with the name of a physical network, and replace INTERFACE with the name of the network interface that will be used to connect to the physical network.
CONFIG_NEUTRON_OVS_TENANT_NETWORK_TYPE vxlan Type of network to allocate for tenant networks. Supported values are: vlan, local, gre, vxlan.
CONFIG_NEUTRON_OVS_VLAN_RANGES  A comma-separated list of VLAN ranges for the OpenStack Networking openvswitch plugin. Each tuple in the list is expected to be in the format PHYSICAL:START:END. Replace PHYSICAL with the name of a physical network, replace START with the start of the VLAN range to identify with it, and replace END with the end of the VLAN range to associate with it Example: physnet1:1:4094,physnet2,physnet3:3000:3999
CONFIG_NEUTRON_OVS_BRIDGE_MAPPINGS A comma-separated list of bridge mappings for the OpenStack Networking openvswitch plugin. Each tuple in the list is expected to be in the format PHYSICAL:BRIDGE. Replace PHYSICAL with the name of a physical network, and replace BRIDGE with the name of the Open vSwitch bridge that will be used to connect to the physical network. Example: physnet1:br-eth1,physnet2:br-eth2,physnet3:br-eth3
CONFIG_NEUTRON_OVS_BRIDGE_IFACES  A comma-separated list of colon-separated Open vSwitch bridge:interface pairs. The interface will be added to the associated bridge.
CONFIG_NEUTRON_OVS_TUNNEL_RANGES  A comma-separated list of tunnel ranges for the OpenStack Networking openvswitch plugin.
CONFIG_NEUTRON_OVS_TUNNEL_IF  Interface for the OVS tunnel; Packstack overrides the IP address used for tunnels on this hypervisor to the IP found on the specified interface (for example, eth1).
CONFIG_NEUTRON_OVS_VXLAN_UDP_PORT 4789 The vxlan UDP port.
CONFIG_HORIZON_SSL n To set up dashboard communication over HTTPS, specify y.
CONFIG_SSL_CERT  PEM encoded certificate to be used for SSL connections to the HTTPS server; leave blank if a certificate should be generated. This certificate must not require a passphrase.
CONFIG_SSL_KEY  Keyfile corresponding to the certificate if one was provided.
CONFIG_SSL_CACHAIN  PEM encoded CA certificates from which the certificate chain of the server certificate can be assembled.
CONFIG_SWIFT_KS_PW Randomly generatedPassword to use for Object Storage to authenticate with Identity.
CONFIG_SWIFT_STORAGES Loopback device is createdA comma-separated list of devices which to use as Object Storage device. Each entry must take the format /path/to/dev, for example /dev/vdb will install /dev/vdb as Object Storage device (Packstack does not create the filesystem, you must do this first).
CONFIG_SWIFT_STORAGE_ZONES 1 Number of Object Storage zones, this number must be no bigger than the number of storage devices configured.
CONFIG_SWIFT_STORAGE_REPLICAS 1 Number of Object Storage replicas, this number must be no bigger than the number of storage zones configured.
CONFIG_SWIFT_STORAGE_FSTYPE ext4 FileSystem type for storage nodes. Supported values are: ext4 and xfs
CONFIG_SWIFT_HASH Custom seed number to use for swift_hash_path_suffix in /etc/swift/swift.conf. If you do not provide a value, a seed number is automatically generated.
CONFIG_SWIFT_STORAGE_SIZE 2G Size of the Object Storage loopback file storage device.
CONFIG_HEAT_DB_PW  Password used by Orchestration (heat) user to authenticate against MariaDB.
CONFIG_HEAT_AUTH_ENC_KEY  Encryption key to use for authentication info in the Orchestration database.
CONFIG_HEAT_KS_PW  Password to use for the Orchestration service to authenticate with Identity.
CONFIG_HEAT_CLOUDWATCH_INSTALL n Specify y if you would like Packstack to install the Orchestration CloudWatch API.
CONFIG_HEAT_CFN_INSTALL n Specify y if you would like Packstack to install the Orchestration CloudFormation API.
CONFIG_HEAT_DOMAIN heat Name of the Identity domain for Orchestration.
CONFIG_HEAT_DOMAIN_ADMIN heat-admin Name of the Identity domain admin user for Orchestration.
CONFIG_HEAT_DOMAIN_PASSWORD Randomly generatedPassword for the Identity domain admin user for Orchestration.
CONFIG_PROVISION_DEMO y Packstack can provision for demo usage and testing. This key selects whether to provision demo OpenStack Networking networks, subnets and routers. Specify y if you want to provision for demo usage and testing. It requires CONFIG_NEUTRON_INSTALL=y and CONFIG_NEUTRON_USE_NAMESPACES=y.
CONFIG_PROVISION_TEMPEST n Packstack can configure Tempest (OpenStack test suite) for running tests against the OpenStack install. Specify y if you want to configure Tempest for testing. It requires CONFIG_NEUTRON_INSTALL=y and CONFIG_NEUTRON_USE_NAMESPACES=y.
CONFIG_PROVISION_TEMPEST_USER The name of the Tempest provisioning user. If you do not provide a user name, Tempest is configured in a standalone mode.
CONFIG_PROVISION_TEMPEST_USER_PW Randomly generatedThe password to use for the Tempest provisioning user.
CONFIG_PROVISION_DEMO_FLOATRANGE 172.24.4.224/28 CIDR network address for the floating IP subnet.
CONFIG_PROVISION_CIRROS_URL http://download.cirros-cloud.net/0.3.3/cirros-0.3.3-x86_64-disk.img URL or local file location for the Cirros demo image to be provided as an initial image in the Image service.
CONFIG_PROVISION_TEMPEST_REPO_URI https://github.com/openstack/tempest.git URI of the Tempest git repository.
CONFIG_PROVISION_TEMPEST_REPO_REVISION master Revision (branch) of the Tempest git repository.
CONFIG_PROVISION_ALL_IN_ONE_OVS_BRIDGE n Packstack allows you to configure the external OVS bridge in an all-in-one deployment. Specify y to set up the L3 external bridge with the appropriate IP address to act as the gateway for Virtual Machines.
CONFIG_CEILOMETER_SECRET Randomly generatedSecret key for signing Telemetry messages.
CONFIG_CEILOMETER_KS_PW Randomly generatedPassword to use for the Telemetry service to authenticate with Identity.
CONFIG_MONGODB_HOST 192.0.43.10 IP address of the server on which to install MongoDB.
CONFIG_NAGIOS_PW Randomly generatedPassword of the nagiosadmin user on the Nagios server.