... | ... | @@ -84,7 +84,7 @@ Please make sure that kea 1.6.0 has been installed and configuration files have |
|
|
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:
|
|
|
* Upgrading `load-balance` setup:
|
|
|
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
|
... | ... | @@ -92,4 +92,36 @@ Please make sure that kea 1.6.0 has been installed and configuration files have |
|
|
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 |
|
|
1. Kea HA setup is upgraded to 1.6.0
|
|
|
|
|
|
**Upgrading 1.4.0-P1 HA setup**
|
|
|
Unfortunately 1.4.0-P1 HA setup can't be upgraded without turning off DHCP service completely. Both Kea 1.5.0 and 1.6.0 has incompatible synchronisation process with 1.4.0-P1. So only option is to move leases files. Procedure is exactly the same for `load-balancing` and `hot-standby` types.
|
|
|
|
|
|
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. Turn off 1.4.0-P1 `standby` server.
|
|
|
1. Turn off 1.4.0-P1 `primary` server.
|
|
|
1. Copy all `kea-leases6.csv*` files from working directory of 1.4.0-P1 to 1.6.0
|
|
|
1. Start Kea 1.6.0 `primary` server, it will detect that lease file is in incorrect version, and rewrite this:
|
|
|
```
|
|
|
HCPSRV_MEMFILE_NEEDS_UPGRADING version of lease file: <installation_path>/var/lib/kea/kea-leases6.csv schema is earlier than version 3.1
|
|
|
DHCPSRV_MEMFILE_CONVERTING_LEASE_FILES running LFC now to convert lease files to the current schema: 2.1
|
|
|
```
|
|
|
5. Start Kea 1.6.0 `standby` server, note that we were not moving files for this one it will synchronise by itself with `primary` server.
|
|
|
6. when synchronisation will be over, upgrade to newest version will be concluded
|
|
|
|
|
|
* Upgrading `load-balance` setup:
|
|
|
1. Turn off 1.4.0-P1 `secondary` server.
|
|
|
1. Turn off 1.4.0-P1 `primary` server.
|
|
|
1. Copy all `kea-leases6.csv*` files from working directory of 1.4.0-P1 to 1.6.0
|
|
|
1. Start Kea 1.6.0 `primary` server, it will detect that lease file is in incorrect version, and rewrite this:
|
|
|
```
|
|
|
HCPSRV_MEMFILE_NEEDS_UPGRADING version of lease file: <installation_path>/var/lib/kea/kea-leases6.csv schema is earlier than version 3.1
|
|
|
DHCPSRV_MEMFILE_CONVERTING_LEASE_FILES running LFC now to convert lease files to the current schema: 2.1
|
|
|
```
|
|
|
5. Start Kea 1.6.0 `secondary` server, note that we were not moving files for this one it will synchronise by itself with `primary` server.
|
|
|
6. when synchronisation will be over, upgrade to newest version will be concluded
|
|
|
|
|
|
Note: upgrade from 1.4.0-P1 to 1.5.0-P1 is exactly the same as for 1.4.0-P1 to 1.6.0 but we recommend going straight to 1.6.0 |
|
|
\ No newline at end of file |