(StrOpt) API version to use for communicating with the ramdisk agent.
+
+
= 1
+
(IntOpt) Number of iterations to be run for erasing devices.
+
= None
(IntOpt) Priority to run in-band erase devices via the Ironic Python Agent ramdisk. If unset, will use the priority set in the ramdisk (defaults to 10 for the GenericHardwareManager). If set to 0, will not run during cleaning.
@@ -45,6 +49,14 @@
= True
(BoolOpt) Whether Ironic will manage TFTP files for the deploy ramdisks. If set to False, you will need to configure your own TFTP server that allows booting the deploy ramdisks.
+
+
= 6
+
(IntOpt) Number of times to retry getting power state to check if bare metal node has been powered off after a soft power off.
+
+
+
= 5
+
(IntOpt) Amount of time (in seconds) to wait between polling power state after trigger soft poweroff.
(IntOpt) Exponent to determine number of hash partitions to use when distributing load across conductors. Larger values will result in more even distribution of load and less load when rebalancing the ring, but more memory usage. Number of partitions per conductor is (2^hash_partition_exponent). This determines the granularity of rebalancing: given 10 hosts, and an exponent of the 2, there are 40 partitions in the ring. A few thousand partitions should make rebalancing smooth in most cases. The default is suitable for up to a few hundred conductors. Too many partitions has a CPU impact.
+
(IntOpt) Exponent to determine number of hash partitions to use when distributing load across conductors. Larger values will result in more even distribution of load and less load when rebalancing the ring, but more memory usage. Number of partitions per conductor is (2^hash_partition_exponent). This determines the granularity of rebalancing: given 10 hosts, and an exponent of the 2, there are 40 partitions in the ring.A few thousand partitions should make rebalancing smooth in most cases. The default is suitable for up to a few hundred conductors. Too many partitions has a CPU impact.
-
= localhost
-
(StrOpt) Name of this node. This can be an opaque identifier. It is not necessarily a hostname, FQDN, or IP address. However, the node name must be valid within an AMQP key, and if using ZeroMQ, a valid hostname, FQDN, or IP address.
+
= sd-52009.dedibox.fr
+
(StrOpt) Name of this node. This can be an opaque identifier. It is not necessarily a hostname, FQDN, or IP address. However, the node name must be valid within an AMQP key, and if using ZeroMQ, a valid hostname, FQDN, or IP address.
= /usr/lib/syslinux/isolinux.bin
@@ -81,17 +81,13 @@
= /etc/ironic/rootwrap.conf
(StrOpt) Path to the rootwrap configuration file to use for running commands as root.
-
-
= True
-
(BoolOpt) Some periodic tasks can be run in a separate process. Should we run them here?
-
= $pybasedir
(StrOpt) Top-level directory for maintaining ironic's state.
-
= None
-
(StrOpt) Explicitly specify the temporary working directory.
+
= /tmp
+
(StrOpt) Temporary working directory, default is Python temp dir.
(StrOpt) Enable eventlet backdoor. Acceptable values are 0, <port>, and <start>:<end>, where 0 results in listening on a random tcp port number; <port> results in listening on the specified port number (and not enabling backdoor if that port is in use); and <start>:<end> results in listening on the smallest unused port number within the specified range of port numbers. The chosen port is displayed in the service's log file.
-
= False
(BoolOpt) Enable pecan debug mode. WARNING: this is insecure and should not be used in a production environment.
(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in M release.
(IntOpt) How often times during the heartbeat_timeout_threshold we check the heartbeat.
-
= 0
-
(IntOpt) Number of seconds after which the Rabbit broker is considered down if heartbeat's keep-alive fails (0 disables the heartbeat, >0 enables it. Enabling heartbeats requires kombu>=3.0.7 and amqp>=1.4.0). EXPERIMENTAL
+
= 60
+
(IntOpt) Number of seconds after which the Rabbit broker is considered down if heartbeat's keep-alive fails (0 disable the heartbeat). EXPERIMENTAL
= 1.0
(FloatOpt) How long to wait before reconnecting in response to an AMQP consumer cancel notification.
+
+
= 60
+
(IntOpt) How long to wait before considering a reconnect attempt to have failed. This value should not be longer than rpc_response_timeout.
+
=
(StrOpt) SSL certification authority file (valid only if SSL enabled).
@@ -106,8 +110,8 @@
(StrOpt) The RabbitMQ virtual host.
-
= 30
-
(IntOpt) Size of RPC connection pool.
+
= False
+
(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in M release.