Table 10.12. XML attributes of a network Element
Attribute | Default | Description |
---|---|---|
add-host
|
TRUE
|
If TRUE, and
ip-range-start is used, Pacemaker will automatically ensure that /etc/hosts inside the containers has entries for each replica name and its assigned IP.
|
ip-range-start
|
|
If specified, Pacemaker will create an implicit
ocf:heartbeat:IPaddr2 resource for each container instance, starting with this IP address, using up to replicas sequential addresses. These addresses can be used from the host’s network to reach the service inside the container, though it is not visible within the container itself. Only IPv4 addresses are currently supported.
|
host-netmask
|
32
| |
host-interface
|
| |
control-port
|
3121
|
If the bundle contains a
primitive , the cluster will use this integer TCP port for communication with Pacemaker Remote inside the container. Changing this is useful when the container is unable to listen on the default port, for example, when the container uses the host’s network rather than ip-range-start (in which case replicas-per-host must be 1), or when the bundle may run on a Pacemaker Remote node that is already listening on the default port. Any PCMK_remote_port environment variable set on the host or in the container is ignored for bundle connections.
|
Note
httpd-bundle
has replicas=2
, its containers will be named httpd-bundle-0
and httpd-bundle-1
.
Table 10.13. Attributes of a port-mapping Element
Note
primitive
, Pacemaker will automatically map the control-port
, so it is not necessary to specify that port in a port-mapping
.