... | ... | @@ -68,26 +68,28 @@ Kea 1.6.0 continues to support the global `logging` section in each server's con |
|
|
|
|
|
**Upgrading HA 1.5.0 setup**
|
|
|
|
|
|
It's possible to upgrade Kea HA setup from 1.5.0 to 1.6.0 without stopping DHCP service in the network but there is specific set of instructions for both types of HA configurations (`load-balancing` and `hot-standby`). The main problem in migrating to newer version is that Kea 1.5.0 is not able to synchronise leases that were handed out by Kea 1.6.0 (Kea 1.6.0 introduced `lease6-bulk-apply` isc-projects/kea#683 isc-projects/kea#689 which is not backward compatible)
|
|
|
It's possible to upgrade Kea HA setup from 1.5.0 to 1.6.0 without stopping the DHCP service for the network but there is a specific set of instructions for both types of HA configuration (`load-balancing` and `hot-standby`).
|
|
|
|
|
|
Please make sure that kea 1.6.0 will be installed and configuration files will be prepared (taking to the account changes described above) **BEFORE** you start this procedure, you don't want to encounter any problems with system while part of your setup is disabled/removed.
|
|
|
The main problem in migrating to the newer version is that Kea 1.5.0 is not able to synchronise leases that were issued by Kea 1.6.0 (Kea 1.6.0 introduced `lease6-bulk-apply` isc-projects/kea#683 isc-projects/kea#689 which is not backward-compatible)
|
|
|
|
|
|
Please make sure that kea 1.6.0 has been installed and configuration files have been prepared (taking into account all the changes described above) **BEFORE** you start this procedure; you don't want to encounter any problems with the system while part of your DHCP HA provisioning is disabled/removed during the upgrade.
|
|
|
|
|
|
* Upgrading `hot-standby` setup:
|
|
|
1. determine which one of kea servers is `standby` this is the one we will start our procedure
|
|
|
1. stop kea 1.5.0 that was working as `standby` (at this point `primary` will still handout leases, so service will be maintained)
|
|
|
1. start kea 1.6.0 also in `standby` and wait as long as it's needed for lease file synchronisation, process will end with log message `[kea-dhcp6.commands/1353] COMMAND_RECEIVED Received command 'dhcp-enable'`
|
|
|
1. go to the system on which kea 1.5.0 in `primary` mode is running
|
|
|
1. turn off `primary` node, at this point DHCP service will be maintained by freshly installed Kea 1.6.0 (if you start procedure with `primary` node than all leases handed out during this point will be lost)
|
|
|
1. start Kea 1.6.0 in `primary` and wait for synchronisation process to finish (this will be much faster than in previous step)
|
|
|
1. at this point Kea 1.6.0 `primary` should have leases handed out before upgrade and with leases handed out by Kea configured in `standby` mode we upgraded first
|
|
|
1. Determine which one of kea servers is `standby` this is the one we will start our procedure.
|
|
|
1. Stop kea 1.5.0 that was working as `standby` (at this point `primary` will still handout leases, so service will be maintained).
|
|
|
1. Start kea 1.6.0 also in `standby` and wait as long as it's needed for lease file synchronisation, process will end with log message `[kea-dhcp6.commands/1353] COMMAND_RECEIVED Received command 'dhcp-enable'`.
|
|
|
1. Go to the system on which kea 1.5.0 in `primary` mode is running.
|
|
|
1. Turn off `primary` node, at this point DHCP service will be maintained by freshly installed Kea 1.6.0 (if you start procedure with `primary` node than all leases handed out during this point will be lost).
|
|
|
1. Start Kea 1.6.0 in `primary` and wait for synchronisation process to finish (this will be much faster than in previous step).
|
|
|
1. At this point Kea 1.6.0 `primary` should have all of the leases handed out before upgrading as well as all of the leases handed out by the Kea instance configured in `standby` mode that we upgraded first.
|
|
|
1. Kea HA setup is upgraded to 1.6.0
|
|
|
|
|
|
* Upgrading `load-balance` setup:
|
|
|
This process is easier to perform because there is no difference in which server will be upgraded first.
|
|
|
1. choose your server for upgrade
|
|
|
1. stop kea 1.5.0 and start kea 1.6.0
|
|
|
1. wait until lease synchronisation is finished
|
|
|
1. go to other 1.5.0 instance
|
|
|
1. stop it and start kea 1.6.0
|
|
|
1. wait until lease synchronisation is finished (it will be much faster than in previous step due to `lease6-bulk-apply` command)
|
|
|
1. This process is easier to perform because there is no difference in which server will be upgraded first.
|
|
|
1. Choose the server to be upgraded first.
|
|
|
1. Stop kea 1.5.0 and start kea 1.6.0
|
|
|
1. Wait until lease synchronisation is finished
|
|
|
1. Go to other 1.5.0 instance
|
|
|
1. Stop it and start kea 1.6.0
|
|
|
1. Wait until lease synchronisation is finished (it will be much faster than in previous step due to `lease6-bulk-apply` command)
|
|
|
1. Kea HA setup is upgraded to 1.6.0 |
|
|
\ No newline at end of file |