Changes between Version 4 and Version 5 of GlobalReservations


Ignore:
Timestamp:
Aug 17, 2018, 11:25:12 PM (15 months ago)
Author:
vicky
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GlobalReservations

    v4 v5  
    11= Global Host Reservations =
    22
    3 The goal of this document is to describe a proposed extension of the host reservation mechanism available in Kea 1.4. Its current limitation is the constraint to tie each host reservation to a given subnet. However, in some cases it makes sense to have a global reservation that would apply to many/all subnets (i.e. it would be used regardless of the place a device is attached to the network).
    4 
    5 == Proposed code changes ==
    6 
    7 Currently it is possible to specify one of three reservation modes: '''disabled''', '''out-of-pool''' and '''all'''. A fourth choice would be implemented, called '''global'''. When specified, it would cause Kea to look up the hosts database for global reservations rather than subnet-specific.
    8 
    9 The global reservations would be designated by using subnet-id equal to 0.
    10 
    11 This would allow:
    12 
    13 1. Users to configure global HR for the whole network.
    14 2. Users to configure different modes on different networks, if needed.
    15 3. Global HRs to specify essentially any parameter possible in host reservations, in particular a hostname among other things.
    16 4. Global HRs to specify a fixed-address, caveat being we do not validate it against known networks.
    17 5. Allow network/subnet specific options to be sent, albeit based on the client's point of attachement (in other words, the subnet selection would continue to work exactly as it does in Kea 1.4)
    18 
    19 == Known limitations ==
    20 
    21 In the initial implementation it would be possible, but discouraged to reserve addresses in global reservations. It would be possible, but Kea wouldn't verify whether the reserved address belong to the network the device is currently visiting. If misused, this could easily lead to clients getting broken configurations.
    22 
    23 When using global reservation in a subnet, a subnet specific mechanism would be disabled. For example, if you have a subnet with subnet-id 1 and global reservations enabled, the hosts database would be queried for subnet-id 0. Reservations with subnet-id 1 would not be used.
    24 
    25 == Timeline ==
    26 
    27 If approved, implementation of this feature would take 10 working days. The untested code may become available sooner, but anyone interested in testing it early must acknowledge that this would be a software that didn't complete its testing cycle yet.
    28 
    29 == Tasks needed ==
    30 
    31 The following tasks are necessary to implement this feature:
    32 
    33  - HR parser, host-cmds, and backends must accept 0 as a subnet id
    34 
    35  - Servers need a mechanism to know to when to do a "global" search (HR_MODE == HR_GLOBAL)
    36 
    37  - AllocEngine::findReservation() -  if the mode is HR_GLOBAL, then it does the same host-id lookup(s) now, but with subnet-id = 0
     3Please see https://gitlab.isc.org/isc-projects/kea/wikis/designs/global-reservations