|
|
The following page describe steps necessary to migrate existing 1.5.0 installations to 1.6.0.
|
|
|
The following page describe steps necessary to migrate existing 1.5.0 installations to 1.6.0.
|
|
|
|
|
|
1. Default file locations for lease file, server-duid, log files and lock files have changed. Files previously stored in `/var/kea` are now stored in `/var/run/kea`. Server hooks previously installed in `/usr/lib/hooks` are now installed in `/usr/lib/kea/hooks`. The log files are now stored in `/var/log/kea`. (#538, #686)
|
|
|
|
|
|
2. The kea-admin commands (lease-init, lease-version, lease-upgrade) were renamed to better reflect the fact that the database can store much more than just leases. They're now called db-init, db-version, db-upgrade. (#466)
|
|
|
2. The kea-admin commands (lease-init, lease-version, lease-upgrade) were renamed to better reflect the fact that the database can store much more than just leases. They're now called db-init, db-version, db-upgrade. (#466)
|
|
|
|
|
|
Kea 1.5.0 and earlier:
|
|
|
```bash
|
... | ... | @@ -70,9 +70,9 @@ Kea 1.6.0 continues to support the global `logging` section in each server's con |
|
|
|
|
|
**Upgrading a pair of Kea servers in High Availabiity mode from Kea 1.5.0**
|
|
|
|
|
|
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`).
|
|
|
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`).
|
|
|
|
|
|
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)
|
|
|
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.
|
|
|
|
... | ... | @@ -125,4 +125,4 @@ DHCPSRV_MEMFILE_CONVERTING_LEASE_FILES running LFC now to convert lease files to |
|
|
5. Start the Kea 1.6.0 `standby` server. Note that we will not move the lease files for this one because it will synchronise leases automatically with the `primary` server.
|
|
|
6. When the synchronisation is complete, the upgrade to the newer Kea version will be finished.
|
|
|
|
|
|
Note: the upgrade from Kea 1.4.0-P1 to Kea 1.5.0-P1 is exactly the same as for Kea 1.4.0-P1 to Kea 1.6.0. We recommend going straight to Kea 1.6.0. |
|
|
\ No newline at end of file |
|
|
Note: the upgrade from Kea 1.4.0-P1 to Kea 1.5.0-P1 is exactly the same as for Kea 1.4.0-P1 to Kea 1.6.0. We recommend going straight to Kea 1.6.0. |