5.3.2. Editing a PackStack Answer File
PackStack answer files are editable in any text editor. Lines preceded with a # character are treated as comments and are ignored.
The table presented here lists the configuration keys available. Configuration values are provided in the answer files as key-value pairs of the form:
KEY=VALUE
Where a key accepts multiple comma separated values, that is noted in the description of the configuration key. Some configuration keys also have command line equivalents, allowing them to be provided directly as arguments to the invocation of the
packstack command. Where this is the case the command line argument is also listed in the table.
Table 5.1. PackStack Configuration Keys
| Configuration Key | Command Line Argument | Default Value | Description |
|---|---|---|---|
CONFIG_SSH_KEY | --sh-public-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_MYSQL_INSTALL | --os-mysql-install | y |
Set to
y if you would like Packstack to install MySQL.
Note
PackStack is capable of installing a single MySQL database node. On the other hand, PackStack does not handle MySQL cluster installation, but it allows you to work with a MySQL cluster that you have set up separately.
If you choose
n, PackStack asks you for credentials and uses CONFIG_MYSQL_HOST as a given remote database.
|
CONFIG_GLANCE_INSTALL | --os-glance-install | y | Set to y if you would like PackStack to install the Image service. |
CONFIG_CINDER_INSTALL | --os-cinder-install | y | Set to y if you would like PackStack to install the Volume service. |
CONFIG_NOVA_INSTALL | --os-nova-install | y | Set to y if you would like PackStack to install the Compute service. |
CONFIG_NEUTRON_INSTALL | --os-neutron-install | y | Set to y if you would like PackStack to install the OpenStack Networking service. |
CONFIG_HORIZON_INSTALL | --os-horizon-install | y | Set to y if you would like PackStack to install the Dashboard service. |
CONFIG_SWIFT_INSTALL | --os-swift-install | n | Set to y if you would like PackStack to install Object Storage. |
CONFIG_CEILOMETER_INSTALL | --os-ceilometer-install | y | Set to y if you would like PackStack to install the Telemetry service. |
CONFIG_HEAT_INSTALL | --os-heat-install | n | Set to y if you would like PackStack to install the Orchestration service. |
CONFIG_CLIENT_INSTALL | --os-client-install | y | Set to y if you would like PackStack to install the OpenStack client packages. An admin "rc" file will also be installed. |
CONFIG_NTP_SERVERS | --ntp-servers | Comma separated list of NTP servers. Leave plain if PackStack should not install ntpd on instances. | |
CONFIG_NAGIOS_INSTALL | --nagios-install | n | Set to y if you would like to install Nagios. Nagios provides additional tools for monitoring the OpenStack environment. |
EXCLUDE_SERVERS | --exclude-servers |
If you have existing servers that have been configured previously, and you do not want PackStack to overwrite their configurations, you can specify a list of IP addresses of the servers to be excluded.
Leave plain if you don't need to exclude any server.
| |
CONFIG_MYSQL_HOST | --mysql-host | 192.0.43.10 | The IP address of the server on which to install MySQL. |
CONFIG_MYSQL_USER | --mysql-user | root | User name for the MySQL administrative user. |
CONFIG_MYSQL_PW | --mysql-pw | Password for the MySQL administrative user. This value is randomly generated if you do not provide it. | |
CONFIG_QPID_HOST | --qpid-host | 192.0.43.10 | The IP address of the server on which to install the QPID service. |
CONFIG_KEYSTONE_HOST | --keystone-host | 192.0.43.10 | The IP address of the server on which to install the Identity service. |
CONFIG_KEYSTONE_DB_PW | --keystone-db-passwd | The password to use for Identity to access the database. This value is randomly generated if you do not provide it. | |
CONFIG_KEYSTONE_ADMIN_TOKEN | --keystone-admin-token | The token to use for the Identity service API. This value is randomly generated if you do not provide it. | |
CONFIG_KEYSTONE_ADMIN_PW | --keystone-admin-passwd | The password to use for the Identity administrative user. This value is randomly generated if you do not provide it. | |
CONFIG_KEYSTONE_DEMO_PW | --keystone-demo-passwd | The password to use for the demo tenant. This value is randomly generated if you do not provide it. Only used if CONFIG_PROVISION_DEMO=y | |
CONFIG_KEYSTONE_TOKEN_FORMAT | --keystone-token-format | UUID | PackStack allows a choice of the token format to be used by Keystone, either UUID or PKI. The current default is UUID, although the recommended format for new deployments is PKI, which will become the default in future. |
CONFIG_GLANCE_HOST | --glance-host | 192.0.43.10 | The IP address of the server on which to install the Image service. |
CONFIG_GLANCE_DB_PW | --glance-db-passwd | The password to use for the Image service to access database. This value is randomly generated if you do not provide it. | |
CONFIG_GLANCE_KS_PW | --glance-ks-passwd | The password to use for the Image service to authenticate with Identity. This value is randomly generated if you do not provide it. | |
CONFIG_CINDER_HOST | --cinder-host | 192.0.43.10 | The IP address of the server on which to install the Volume service. |
CONFIG_CINDER_DB_PW | --cinder-db-passwd | The password to use for the Volume service to access database. This value is randomly generated if you do not provide it. | |
CONFIG_CINDER_KS_PW | --cinder-ks-passwd | The password to use for the Volume service to authenticate with Identity. This value is randomly generated if you do not provide it. | |
CONFIG_CINDER_BACKEND | --cinder-backend | lvm | Cinder backend to use, valid options are: lvm, gluster, nfs |
CONFIG_CINDER_VOLUMES_CREATE | --cinder-volumes-create | y |
PackStack expects storage for use with the Volume service to be available on a volume group named
cinder-volumes. If this volume group does not already exist then PackStack is able to create it automatically.
Selecting
y means that PackStack will create raw disk image in the /var/lib/cinder and mount it for use by the Volume service using a loopback device.
|
CONFIG_CINDER_VOLUMES_SIZE | --cinder-volumes-size | 20G |
If you elected to have PackStack create the
cinder-volumes volume group for you then you will need to provide the desired size of it in gigabytes (GB).
|
CONFIG_CINDER_GLUSTER_MOUNTS | --cinder-gluster-mounts |
A single or comma separated list of gluster volume shares to mount, eg: ip-address:/vol-name
| |
CONFIG_CINDER_NFS_MOUNTS | --cinder-nfs-mounts | 20G |
A single or comma separated list of NFS exports to mount, eg: ip-address:/export-name
|
CONFIG_NOVA_API_HOST | --novaapi-host | 192.0.43.10 | The IP address of the server on which to install the Compute API service. |
CONFIG_NOVA_CERT_HOST | --novacert-host | 192.0.43.10 | The IP address of the server on which to install the Compute Certificate service. |
CONFIG_NOVA_VNCPROXY_HOST | --novavncproxy-hosts | 192.0.43.10 | The IP address of the server on which to install the Compute VNC proxy. |
CONFIG_NOVA_COMPUTE_HOSTS | --novacompute-hosts | 192.0.43.10 | A comma separated list of IP addresses on which to install the Compute services. |
CONFIG_NOVA_CONDUCTOR_HOST | --novaconductor-hosts | 192.0.43.10 | The IP address of the server on which to install the Conductor services |
CONFIG_NOVA_DB_PW | --nova-db-passwd | The password to use for Compute to access the database. This value is randomly generated if you do not provide it. | |
CONFIG_NOVA_KS_PW | --nova-ks-passwd | The password to use for Compute to authenticate with Identity. This value is randomly generated if you do not provide it. | |
CONFIG_NOVA_SCHED_HOST | --novasched-host | 192.0.43.10 | The IP address of the server on which to install the Compute Scheduler service. |
CONFIG_NOVA_SCHED_CPU_ALLOC_RATIO | --novasched-cpu-allocation-ratio | 16.0 | The overcommitment ratio for virtual to physical CPUs. Set to 1.0 to disable CPU overcommitment. |
CONFIG_NOVA_SCHED_RAM_ALLOC_RATIO | --novasched-ram-allocation-ratio | 1.5 | The overcommitment ratio for virtual to physical RAM. Set to 1.0 to disable RAM overcommitment. |
CONFIG_NOVA_COMPUTE_PRIVIF | --novacompute-privif | eth1 | Private interface for Flat DHCP on the Compute servers. |
CONFIG_NOVA_NETWORK_HOSTS | --novanetwork-hosts | 192.0.43.10 | The IP address of the server on which to install the Compute Network service.
This option is available if you have selected compute networking.
|
CONFIG_NOVA_NETWORK_MANAGER | --novanetwork-manager | Compute Network Manager. | |
CONFIG_NOVA_NETWORK_PUBIF | --novanetwork-pubif | eth0 | Public interface on the Compute network server. |
CONFIG_NOVA_NETWORK_PRIVIF | --novanetwork-privif | eth1 | Private interface for Flat DHCP on the Compute network server. |
CONFIG_NOVA_NETWORK_FIXEDRANGE | --novanetwork-fixed-range | 192.168.32.0/22 | IP Range for Flat DHCP. |
CONFIG_NOVA_NETWORK_FLOATRANGE | --nova-network-floating-range | 10.3.4.0/22 | IP Range for Floating IP addresses. |
CONFIG_NOVA_NETWORK_DEFAULTFLOATINGPOOL | --novanetwork-default-floating-pool | nova | Name of the default floating pool to which the specified floating ranges are added to. |
CONFIG_NOVA_NETWORK_AUTOASSIGNFLOATINGIP | --novanetwork-auto-assign-floating-ip | n | Automatically assign a floating IP to new instances. |
CONFIG_NOVA_NETWORK_VLAN_START | --novanetwork-vlan-start | First VLAN for private networks. | |
CONFIG_NOVA_NETWORK_NUMBER | --novanetwork-num-networks | n | Number of networks to support. |
CONFIG_NOVA_NETWORK_SIZE | --novanetwork-network-size | n | Number of addresses in each private subnet. |
CONFIG_NEUTRON_SERVER_HOST | --neutron-server-host | 192.0.43.10 | The IP addresses of the server on which to install the OpenStack Networking server. |
CONFIG_NEUTRON_USE_NAMESPACES | --neutron-use-namespaces | y | Enable network namespaces for OpenStack Networking. |
CONFIG_NEUTRON_KS_PW | --neutron-ks-password | 192.0.43.10 | The password to use for OpenStack Networking to authenticate with Keystone. |
CONFIG_NEUTRON_DB_PW | --neutron-db-password | The password to use for OpenStack Networking to access database. | |
CONFIG_NEUTRON_L3_HOSTS | --neutron-l3-hosts | 192.0.43.10 | A comma separated list of IP addresses on which to install OpenStack Networking L3 agent. |
CONFIG_NEUTRON_L3_EXT_BRIDGE | --neutron-l3-ext-bridge | br-ex | The name of the bridge that the OpenStack Networking L3 agent will use for external traffic. Leave this option blank if you intend to use a provider network to handle external traffic. |
CONFIG_NEUTRON_DHCP_HOSTS | --neutron-dhcp-hosts | 192.0.43.10 | A comma separated list of IP addresses on which to install OpenStack Networking DHCP agent. |
CONFIG_NEUTRON_L2_PLUGIN | --neutron-l2-plugin | openvswitch | The name of the L2 plugin to be used with OpenStack Networking. |
CONFIG_NEUTRON_METADATA_HOSTS | --neutron-metadata-hosts | 192.0.43.10 | A comma separated list of IP addresses on which to install OpenStack Networking metadata agent. |
CONFIG_NEUTRON_METADATA_PW | --neutron-metadata-pw | Password for OpenStack Networking metadata agent. | |
CONFIG_NEUTRON_LB_TENANT_NETWORK_TYPE | --neutron-lb-tenant-network-type | local | The type of network to allocate for tenant networks. Supported values are local and vlan. For multi-node deployments vlan is recommended. |
CONFIG_NEUTRON_LB_VLAN_RANGES | --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. | |
CONFIG_NEUTRON_LB_INTERFACE_MAPPINGS | --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 | --neutron-ovs-tenant-network-type | local | The type of network to allocate for tenant networks. Supported values are local and vlan. For multi-node deployments vlan is recommended. |
CONFIG_NEUTRON_OVS_VLAN_RANGES | --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. | |
CONFIG_NEUTRON_OVS_BRIDGE_MAPPINGS | --neutron-ovs-bridge-mappings | physnet1:br-eth1 | 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. |
CCONFIG_NEUTRON_OVS_TUNNEL_RANGES | --neutron-ovs-tunnel-ranges | A comma separated list of tunnel ranges for the Neutron openvswitch plugin. | |
CONFIG_NEUTRON_OVS_TUNNEL_IF | --neutron-ovs-tunnel-if | Override the IP used for GRE tunnels on this hypervisor to the IP address found on the specified interface (defaults to the HOST IP). | |
CONFIG_OSCLIENT_HOST | --osclient-host | 192.0.43.10 | The IP address of the server on which to install the OpenStack client packages. An admin "rc" file will also be installed. |
CONFIG_HORIZON_HOST | --os-horizon-host | 192.0.43.10 | The IP address of the server on which to install Dashboard. |
CONFIG_HORIZON_SSL | --os-horizon-ssl | n | To set up Dashboard communication over HTTPS set this parameter to y. |
CONFIG_SSL_CERT | --os-ssl-cert | PEM encoded certificate to be used for SSL connections to the HTTPS server, leave blank if one should be generated. This certificate must not require a passphrase. | |
CONFIG_SSL_KEY | --os-ssl-key | Keyfile corresponding to the certificate if one was provided. | |
CONFIG_SWIFT_PROXY_HOSTS | --os-swift-proxy | 192.0.43.10 | The IP address on which to install the Object Storage proxy service. |
CONFIG_SWIFT_KS_PW | --os-swift-ks-passwd | The password to use for Object Storage to authenticate with Identity. This value is randomly generated if you do not provide it. | |
CONFIG_SWIFT_STORAGE_HOSTS | --os-swift-storage | 192.0.43.10 | A comma separated list of IP addresses on which to install the Object Storage services, each entry should take the format IP[/DEVICE], for example 192.0.43.10/vdb will install /dev/vdb on 192.0.43.10 as a Object Storage device, if /DEVICE is omitted PackStack will create a loopback device for a test setup. |
CONFIG_SWIFT_STORAGE_ZONES | --os-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 | --os-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 | --os-swift-storage-fstype | ext4 | FileSystem type for storage nodes. Supported values are ext4 and xfs at this time. |
CONFIG_PROVISION_DEMO | --provision-demo | n (y for allinone) | PackStack can provision for demo usage and testing. This key selects whether to provision demo OpenStack Networking networks, subnets and routers. Set to 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_DEMO will be enabled if you run packstack --allinone and CONFIG_NEUTRON_INSTALL=y, which it is by default. |
CONFIG_PROVISION_DEMO_FLOATRANGE | --provision-demo-floatrange | The CIDR network address for the floating IP subnet. | |
CONFIG_PROVISION_TEMPEST | --provision-tempest | n | PackStack can configure Tempest (OpenStack test suite) for running tests against the OpenStack install. Set to y if you want to configure Tempest for testing. It requires CONFIG_NEUTRON_INSTALL=y and CONFIG_NEUTRON_USE_NAMESPACES=y |
CONFIG_PROVISION_TEMPEST_REPO_URI | --provision-tempest-repo-uri | The uri of the tempest git repository to use. | |
CONFIG_PROVISION_TEMPEST_REPO_REVISION | --provision-tempest-repo-revision | The revision of the tempest git repository to use. | |
CONFIG_PROVISION_ALL_IN_ONE_OVS_BRIDGE | --provision-all-in-one-ovs-bridge | n (y for allinone) | PackStack allows you to configure the external OVS bridge in an all-in-one deployment. This sets up the L3 external bridge with the appropriate IP address to act as the gateway for Virtual Machines. Set to y if you want to configure the external OVS bridge. CONFIG_PROVISION_ALL_IN_ONE_OVS_BRIDGE will be enabled if you run packstack --allinone and CONFIG_NEUTRON_INSTALL=y, which it is by default. |
CONFIG_HEAT_HOST | --heat-host | 192.0.43.10 | The IP address of the server on which to install the Heat service. |
CONFIG_HEAT_DB_PW | --heat-mysql-password | The password used by Heat user to authenticate against MySQL. | |
CONFIG_HEAT_KS_PW | --heat-ks-passwd | 192.0.43.10 | The password to use for the Heat service to authenticate with Keystone. |
CONFIG_HEAT_CLOUDWATCH_INSTALL | --os-heat-cloudwatch-install | n | Set to y if you would like Packstack to install Heat CloudWatch. |
CONFIG_HEAT_CFN_INSTALL | --os-heat-cfn-install | n | Set to y if you would like Packstack to install Heat CloudFormation API. |
CONFIG_HEAT_CLOUDWATCH_HOST | --heat-api-cloudwatch-host | 192.0.43.10 | The IP address of the server on which to install Heat CloudWatch API service. |
CONFIG_HEAT_CFN_HOST | --heat-api-cfn-host | 192.0.43.10 | The IP address of the server on which to install Heat CloudFormation API service. |
CONFIG_CEILOMETER_HOST | --ceilometer-host | 192.0.43.10 | The IP address of the server on which to install Ceilometer. |
CONFIG_CEILOMETER_SECRET | --ceilometer-secret | 192.0.43.10 | Secret key for signing Telemetry messages. |
CONFIG_CEILOMETER_KS_PW | --ceilometer-ks-passwd | The password to use for Ceilometer to authenticate with Keystone. | |
CONFIG_USE_EPEL | --use-epel | n | To subscribe each server to EPEL enter y. |
CONFIG_REPO | --additional-repo | A comma separated list of URLs to any additional yum repositories to install. | |
CONFIG_RH_USER | --rh-username | To subscribe each server with Red Hat Subscription Manager, include this with CONFIG_RH_PW. | |
CONFIG_RH_PW | --rh-password | To subscribe each server with Red Hat Subscription Manager, include this with CONFIG_RH_USER. | |
CONFIG_RH_BETA_REPO | --rh-beta-repo | n | To subscribe each server to the Red Hat Enterprise Linux Beta repository set this configuration key to y. This is only required for preview releases of Red Hat Enterprise Linux OpenStack Platform. |
CONFIG_SATELLITE_URL | --rhn-satellite-server | 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_USERNAME | --rhn-satellite-username |
Satellite servers require a user name for authentication. If using Satellite to distribute packages to your systems then you must set this configuration key to your Satellite user name or provide an access key for authentication.
If you intend to use an access key for Satellite authentication then leave this configuration key blank.
| |
CONFIG_SATELLITE_PW | --rhn-satellite-password |
Satellite servers require a password for authentication. If using Satellite to distribute packages to your systems then you must set this configuration key to your Satellite password or provide an access key for authentication.
If you intend to use an access key for Satellite authentication then leave this configuration key blank.
| |
CONFIG_SATELLITE_AKEY | --rhn-satellite-activation-key |
Satellite servers are able to accept an access key for authentication. Set this configuration key to your Satellite access key if you have one.
If you intend to use a user name and password for Satellite authentication then leave this configuration key blank.
| |
CONFIG_SATELLITE_CACERT | --rhn-satellite-cacert |
Specify the path to the certificate of the certificate authority that is used to verify that the connection with the Satellite server is secure. Leave this configuration key blank if you are not using Satellite in your deployment.
| |
CONFIG_SATELLITE_PROFILE | --rhn-satellite-profile |
Specify the profile name that must be used to identify the system in Red Hat Network, if you require one.
| |
CONFIG_SATELLITE_FLAGS | --rhn-satellite-flags |
Specify any additional Satellite flags that you need 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.
Refer to the Red Hat Satellite documentation for more information.
| |
CONFIG_SATELLITE_PROXY | --rhn-satellite-proxy-host |
Specify the HTTP proxy that must be used when connecting to the Satellite server, if required.
| |
CONFIG_SATELLITE_PROXY_USER | --rhn-satellite-proxy-username |
Specify the user name for authenticating with the HTTP proxy that must be used when connecting to the Satellite server, if required.
| |
CONFIG_SATELLITE_PROXY_PW | --rhn-satellite-proxy-password |
Specify the password for authenticating with the HTTP proxy server that must be used when connecting to the Satellite server, if required.
| |
CONFIG_NAGIOS_HOST | --nagios-host | The IP address of the server on which to install Nagios. | |
CONFIG_NAGIOS_PW | --nagios-passwd | The password of the nagiosadmin user on the Nagios server. This value will be randomly generated if it is not provided. |
Important
The amount of space selected for
CINDER_VOLUMES_SIZE must be available on the device used for /var/lib/cinder.
Important
Remember that the size of the volume group will restrict the amount of disk space that you can expose to Compute instances.
Important
PackStack registers systems to Red Hat Network using Subscription Manager. You may encounter problems if your systems have already been registered and subscribed to the Red Hat OpenStack channels using RHN Classic.