Commit f6b0c663 authored by Marcin Siodelski's avatar Marcin Siodelski

[5381] Updated User's Guide according to a review.

Include prefixes in the paragraph about pool usage within shared networks.
parent f27fdc7c
...@@ -3516,7 +3516,7 @@ src/lib/dhcpsrv/cfg_host_operations.cc --> ...@@ -3516,7 +3516,7 @@ src/lib/dhcpsrv/cfg_host_operations.cc -->
subnet before it starts allocating addresses from other subnets belonging to subnet before it starts allocating addresses from other subnets belonging to
the same shared network. However, in certain situations the client can be the same shared network. However, in certain situations the client can be
allocated an address from the other subnets before the address pools in the allocated an address from the other subnets before the address pools in the
first subnet get exhausted. That is, when the client provides a hint that first subnet get exhausted, e.g. when the client provides a hint that
belongs to another subnet or the client has reservations in a different than belongs to another subnet or the client has reservations in a different than
default subnet. default subnet.
</para> </para>
...@@ -3526,8 +3526,8 @@ src/lib/dhcpsrv/cfg_host_operations.cc --> ...@@ -3526,8 +3526,8 @@ src/lib/dhcpsrv/cfg_host_operations.cc -->
server doesn't allocate addresses from other subnets until it uses all server doesn't allocate addresses from other subnets until it uses all
the addresses from the first subnet in the shared network. Apart from the the addresses from the first subnet in the shared network. Apart from the
fact that hints, host reservations and client classification affect subnet fact that hints, host reservations and client classification affect subnet
selection, it is also considered that we will enhance allocation strategies selection, it is also foreseen that we will enhance allocation strategies
within a shared network in the future versions of Kea, so as the selection for shared networks in the future versions of Kea, so as the selection
of subnets within a shared network is equally probable (unpredictable).</para> of subnets within a shared network is equally probable (unpredictable).</para>
</note> </note>
......
...@@ -3063,29 +3063,29 @@ If not specified, the default value is: ...@@ -3063,29 +3063,29 @@ If not specified, the default value is:
modems. In this case, the distinction is based on the type of device, rather modems. In this case, the distinction is based on the type of device, rather
than coming out of running out address space.</para> than coming out of running out address space.</para>
<para>A client connected to a shared network may be assigned an address from <para>A client connected to a shared network may be assigned a lease (address
any of the address pools defined within the subnets belonging to the shared or prefix) from any of the pools defined within the subnets belonging to the
network. Internally, the server selects one of the subnets belonging to a shared network. Internally, the server selects one of the subnets belonging to the
shared network and tries to allocate an address from this subnet. If the shared network and tries to allocate a lease from this subnet. If the
server is unable to allocate an address from the selected subnet (e.g. due server is unable to allocate a lease from the selected subnet (e.g. due
to address pools exhaustion) it will use another subnet from the same shared to pools exhaustion) it will use another subnet from the same shared
network and try to allocate an address from this subnet etc. Therefore, in the network and try to allocate a lease from this subnet etc. Therefore, in the
typical case, the server will allocate all addresses available for a given typical case, the server will allocate all leases available in a given
subnet before it starts allocating addresses from other subnets belonging to subnet before it starts allocating leases from other subnets belonging to
the same shared network. However, in certain situations the client can be the same shared network. However, in certain situations the client can be
allocated an address from the other subnets before the address pools in the allocated a lease from the other subnets before the pools in the first
first subnet get exhausted. That is, when the client provides a hint that subnet get exhausted, e.g. when the client provides a hint that belongs
belongs to another subnet or the client has reservations in a different than to another subnet or the client has reservations in a different than
default subnet. default subnet.
</para> </para>
<note> <note>
<para>It is strongly discouraged for the Kea deployments to assume that the <para>It is strongly discouraged for the Kea deployments to assume that the
server doesn't allocate addresses from other subnets until it uses all server doesn't allocate leases from other subnets until it uses all
the addresses from the first subnet in the shared network. Apart from the the leases from the first subnet in the shared network. Apart from the
fact that hints, host reservations and client classification affect subnet fact that hints, host reservations and client classification affect subnet
selection, it is also considered that we will enhance allocation strategies selection, it is also foreseen that we will enhance allocation strategies
within a shared network in the future versions of Kea, so as the selection for shared networks in the future versions of Kea, so as the selection
of subnets within a shared network is equally probable (unpredictable).</para> of subnets within a shared network is equally probable (unpredictable).</para>
</note> </note>
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment