Kea issueshttps://gitlab.isc.org/isc-projects/kea/-/issues2018-09-30T19:38:12Zhttps://gitlab.isc.org/isc-projects/kea/-/issues/18lib process unable to handle more than one configuration (staging and running)2018-09-30T19:38:12ZFrancis Dupontlib process unable to handle more than one configuration (staging and running)According to trac3543 review the lib process lacks a versioning feature as dhcpsrv cfgmgr provides.According to trac3543 review the lib process lacks a versioning feature as dhcpsrv cfgmgr provides.Kea1.5-beta1Francis DupontFrancis Duponthttps://gitlab.isc.org/isc-projects/kea/-/issues/128Use lib process daemon code in netconf2018-10-06T00:51:14ZFrancis DupontUse lib process daemon code in netconfNote I fixed the compilation but there are still some replacement codes waiting for dhcpsrv -> process migration which was done.Note I fixed the compilation but there are still some replacement codes waiting for dhcpsrv -> process migration which was done.Kea1.5-beta1Francis DupontFrancis Duponthttps://gitlab.isc.org/isc-projects/kea/-/issues/32Extend DHCP configuration to point to the config backend2018-10-08T13:05:34ZGhost UserExtend DHCP configuration to point to the config backendWe need at least two configuration parameters: *config-database* and *server-tag* for DHCP servers.
See the https://gitlab.isc.org/isc-projects/kea/wikis/designs/configuration-in-db-design.
We need at least two configuration parameters: *config-database* and *server-tag* for DHCP servers.
See the https://gitlab.isc.org/isc-projects/kea/wikis/designs/configuration-in-db-design.
Kea1.5-beta1Thomas MarkwalderThomas Markwalderhttps://gitlab.isc.org/isc-projects/kea/-/issues/154Netconf reload behavior is not defined2018-10-10T10:24:31ZFrancis DupontNetconf reload behavior is not definedNot a real problem as it does not need to be define/design ASAP.
Creating a MR to disable reload on SIGHUP.Not a real problem as it does not need to be define/design ASAP.
Creating a MR to disable reload on SIGHUP.Kea1.5-beta1Francis DupontFrancis Duponthttps://gitlab.isc.org/isc-projects/kea/-/issues/157config-get API call returns error with some MySQL backend options2018-10-10T16:02:53ZBrian Conryconfig-get API call returns error with some MySQL backend optionsname: config-get API call returns error with some MySQL backend options
about: this looks to be similar to the issue with the Cassandra backend options
```
2018-10-08 11:49:22.742 INFO [kea-dhcp4.dhcpsrv/18240] DHCPSRV_MYSQL_DB opening...name: config-get API call returns error with some MySQL backend options
about: this looks to be similar to the issue with the Cassandra backend options
```
2018-10-08 11:49:22.742 INFO [kea-dhcp4.dhcpsrv/18240] DHCPSRV_MYSQL_DB opening MySQL lease database: host=mysql01 lfc-interval=0 max-reconnect-tries=10 name=keadb password=***** port=3306 reconnect-wait-time=3 type=mysql universe=4 user=keauser
2018-10-08 11:49:22.766 INFO [kea-dhcp4.hosts/18240] DHCPSRV_MYSQL_HOST_DB opening MySQL hosts database: host=mysql01 max-reconnect-tries=10 name=keadb password=***** port=3306 reconnect-wait-time=3 type=mysql universe=4 user=keauser
2018-10-08 11:49:22.783 INFO [kea-dhcp4.dhcp4/18240] DHCP4_STARTED Kea DHCPv4 server version 1.4.0-P1 started
...
2018-10-08 11:49:42.843 INFO [kea-dhcp4.commands/18240] COMMAND_RECEIVED Received command 'config-get'
2018-10-08 11:49:42.844 WARN [kea-dhcp4.commands/18240] COMMAND_PROCESS_ERROR2 Error while processing command: unknown DB access parameter: max-reconnect-tries=10
```https://gitlab.isc.org/isc-projects/kea/-/issues/147*.pid files are created in incorrect place2018-10-12T13:37:02ZWlodzimierz Wencel*.pid files are created in incorrect placePID files are created in /
```
test@debian8-64-1-dhcp:~/jenkins_lab/var/area_A/sbin$ ls -la /
total 104
drwxr-xr-x 22 root root 4096 Oct 1 02:58 .
drwxr-xr-x 22 root root 4096 Oct 1 02:58 ..
drwxr-xr-x 2 root root 4096 Nov 9 ...PID files are created in /
```
test@debian8-64-1-dhcp:~/jenkins_lab/var/area_A/sbin$ ls -la /
total 104
drwxr-xr-x 22 root root 4096 Oct 1 02:58 .
drwxr-xr-x 22 root root 4096 Oct 1 02:58 ..
drwxr-xr-x 2 root root 4096 Nov 9 2017 bin
drwxr-xr-x 3 root root 4096 Nov 9 2017 boot
drwxr-xr-x 17 root root 3240 Jan 12 2018 dev
drwxr-xr-x 97 root root 4096 Oct 1 02:21 etc
drwxr-xr-x 4 root root 4096 Mar 29 2013 home
lrwxrwxrwx 1 root root 31 Nov 9 2017 initrd.img -> /boot/initrd.img-3.16.0-4-amd64
lrwxrwxrwx 1 root root 30 Mar 29 2013 initrd.img.old -> /boot/initrd.img-3.2.0-4-amd64
-rw-r--r-- 1 root root 6 Oct 1 02:58 kea.kea-ctrl-agent.pid
-rw-r--r-- 1 root root 6 Oct 1 02:50 kea.kea-dhcp6.pid
-rw-r--r-- 1 root root 6 Oct 1 02:54 kea.kea-dhcp-ddns.pid
```
even if kea was installed with prefix: /home/test/jenkins_lab/var/area_A/
```
$ ./configure --prefix=/home/test/jenkins_lab/var/area_A/ --with-pgsql --with-mysql --enable-shell
```
and because keactrl has coded correct prefix:
```
test@debian8-64-1-dhcp:~/jenkins_lab/var/area_A/sbin$ cat keactrl | grep prefix
local pid_file_dir=${prefix}/var/kea
prefix=/home/test/jenkins_lab/var/area_A
export KEA_LOGGER_DESTINATION=${prefix}/var/kea/kea.log
prefix=/home/test/jenkins_lab/var/area_A
keactrl_conf=${prefix}/etc/kea/keactrl.conf
```
it's unable to detect if kea is running.Kea1.5-beta1https://gitlab.isc.org/isc-projects/kea/-/issues/169weird error message when kea-netconf is missing -c option2018-10-16T18:53:05ZWlodzimierz Wencelweird error message when kea-netconf is missing -c option```
sudo ./kea-netconf
2018-10-16 06:14:12.687 FATAL [kea-netconf.dctl/23896] DCTL_PID_FILE_ERROR Netconf could not create a PID file: Daemon::makePIDFileName config file name is not set
Service failed: Launch failed: Daemon::makePIDFil...```
sudo ./kea-netconf
2018-10-16 06:14:12.687 FATAL [kea-netconf.dctl/23896] DCTL_PID_FILE_ERROR Netconf could not create a PID file: Daemon::makePIDFileName config file name is not set
Service failed: Launch failed: Daemon::makePIDFileName config file name is not set
```
shouldn't that message be more like 'missing config file' and not speaking about PID file?https://gitlab.isc.org/isc-projects/kea/-/issues/166Kea HA load balancing setup API failed to communicate with DHCP42018-10-17T05:30:25ZGhost UserKea HA load balancing setup API failed to communicate with DHCP4Describe the bug
HA load balancing setup not working with API failed to communicate with dhcp4 server
Server 1 primary
018-10-15 06:25:57.954 WARN [kea-dhcp4.ha-hooks/12395] HA_HEARTBEAT_FAILED heartbeat to (http://10.25.133.12:8080/) f...Describe the bug
HA load balancing setup not working with API failed to communicate with dhcp4 server
Server 1 primary
018-10-15 06:25:57.954 WARN [kea-dhcp4.ha-hooks/12395] HA_HEARTBEAT_FAILED heartbeat to (http://10.25.133.12:8080/) failed: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline, error code 1
2018-10-15 06:26:08.967 WARN [kea-dhcp4.ha-hooks/12395] HA_HEARTBEAT_FAILED heartbeat to (http://10.25.133.12:8080/) failed: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline, error code 1
2018-10-15 06:26:19.981 WARN [kea-dhcp4.ha-hooks/12395] HA_HEARTBEAT_FAILED heartbeat to (http://10.25.133.12:8080/) failed: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline, error code 1
2018-10-15 06:26:30.994 WARN [kea-dhcp4.ha-hooks/12395] HA_HEARTBEAT_FAILED heartbeat to (http://10.25.133.12:8080/) failed: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline, error code 1
2018-10-15 06:26:42.008 WARN [kea-dhcp4.ha-hooks/12395] HA_HEARTBEAT_FAILED heartbeat to (http://10.25.133.12:8080/) failed: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline, error code 1
Server 2 secondary
[root@test2 tmp]# keactrl status
DHCPv4 server: active
DHCPv6 server: active
DHCP DDNS: inactive
Control Agent: active
Kea DHCPv4 configuration file: /etc/kea/kea-dhcp4.conf
Kea DHCPv6 configuration file: /etc/kea/kea-dhcp6.conf
Kea DHCP DDNS configuration file: /etc/kea/kea-dhcp-ddns.conf
Kea Control Agent configuration file: /etc/kea/kea-ctrl-agent.conf
keactrl configuration file: /etc/kea/keactrl.conf
[root@test2 tmp]# ps -aef | grep kea
root 29062 1 0 06:27 pts/2 00:00:00 /usr/sbin/kea-dhcp4 -c /etc/kea/kea-dhcp4.conf
root 29069 1 0 06:27 pts/2 00:00:00 /usr/sbin/kea-dhcp6 -c /etc/kea/kea-dhcp6.conf
root 29078 1 0 06:27 pts/2 00:00:00 /usr/sbin/kea-ctrl-agent -c /etc/kea/kea-ctrl-agent.conf
root 29131 4193 0 06:31 pts/2 00:00:00 grep --color=auto kea
-agent.commands/29078] COMMAND_RECEIVED Received command 'ha-heartbeat'
2018-10-15 06:29:04.182 INFO [kea-ctrl-agent.commands/29078] COMMAND_RECEIVED Received command 'ha-heartbeat'
2018-10-15 06:29:15.196 INFO [kea-ctrl-agent.commands/29078] COMMAND_RECEIVED Received command 'ha-heartbeat'
2018-10-15 06:28:59.221 WARN [kea-dhcp4.ha-hooks/29062] HA_HEARTBEAT_FAILED heartbeat to (http://10.25.133.13:8080/) failed: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline, error code 1
2018-10-15 06:29:10.236 WARN [kea-dhcp4.ha-hooks/29062] HA_HEARTBEAT_FAILED heartbeat to (http://10.25.133.13:8080/) failed: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline, error code 1
2018-10-15 06:29:21.249 WARN [kea-dhcp4.ha-hooks/29062] HA_HEARTBEAT_FAILED heartbeat to (http://10.25.133.13:8080/) failed: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline, error code 1
2018-10-15 06:29:32.264 WARN [kea-dhcp4.ha-hooks/29062] HA_HEARTBEAT_FAILED heartbeat to (http://10.25.133.13:8080/) failed: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline, error code 1
2018-10-15 06:29:43.277 WARN [kea-dhcp4.ha-hooks/29062] HA_HEARTBEAT_FAILED heartbeat to (http://10.25.133.13:8080/) failed: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline, error code 1
To Reproduce
Steps to reproduce the behavior:
Run Kea (which daemon? dhcpv4, dhcpv6, ddns, ca?) with the following config '...'
configure kea HA with load balancing setup
A client does A and sends packet B with options C,D,E via relay F that does '...'
client A sends heartbeat but client B failed to handle both clients are same
The server then '...'
See error
failed: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline, error code 1
Environment:
Kea version: which release? if it's compiled from git, which revision. Use kea-dhcp4 -V to find out.
kea-dhcp4 -V
**
1.4.0
tarball
linked with:
log4cplus 1.1.3
OpenSSL 1.0.2k-fips 26 Jan 2017
database:
MySQL backend 6.0, library 5.5.60-MariaDB
Memfile backend 2.0
**
OS: [e.g. Ubuntu 16.04 x64]
Centos 7 x64
Which features were compiled in (in particular which backends)
If/which hooks where loaded in
control agent config :
{
"Control-agent": {
"http-host": "10.25.133.13",
"http-port": 8080,
"control-sockets": {
"dhcp4": {
"socket-type": "unix",
"socket-name": "/tmp/socket.sock"
},
"dhcp6": {
"socket-type": "unix",
"socket-name": "/tmp/socket.sock"
}
},
"hooks-libraries": [{
"library": "/usr/local/lib/hooks/libdhcp_lease_cmds.so"
},
{
"library": "/usr/local/lib/hooks/libdhcp_stat_cmds.so"
}
]
},
"Logging": {
"loggers": [{
"name": "kea-ctrl-agent",
"severity": "DEBUG",
"output_options": [{
"output": "/usr/local/var/log/kea-ctrl-agent.log"
}]
}]
}
}
**kea-dhcp4.conf :**
> {
> "Dhcp4": {
> "interfaces-config": {
> "interfaces": ["ens160"],
> "dhcp-socket-type": "raw"
>
> },
>
> "valid-lifetime": 60000,
> "renew-timer": 10000,
> "rebind-timer": 20000,
> "subnet4": [{
>
> "id": 2,
> "subnet": "10.25.133.0/24",
> "pools": [{
> "pool": "10.25.133.2-10.25.133.100"
> }]
>
> }],
>
> "lease-database": {
> "type": "mysql",
> "name": "kea",
> "user": "kea",
> "password": "***",
> "host": "10.25.133.13",
> "port": 3306
> },
>
> "hosts-database": {
> "type": "mysql",
> "name": "kea",
> "user": "kea",
> "password": "***",
> "host": "10.25.133.13",
> "port": 3306
> },
> "hooks-libraries": [{
> "library": "/usr/lib64/hooks/libdhcp_lease_cmds.so"
> },
>
> {
> "library": "/usr/lib64/hooks/libdhcp_stat_cmds.so"
>
> },
>
> {
> "library": "/usr/lib64/hooks/libdhcp_ha.so",
> "parameters": {
> "high-availability": [{
> "this-server-name": "test2",
> "mode": "load-balancing",
> "heartbeat-interval": 60,
> "max-response-delay": 100,
> "max-ack-delay": 100,
> "max-unacked-messages": 10,
> "peers": [{
> "name": "test3",
> "url": "http://10.25.133.13:8080/",
> "role": "primary",
> "auto-failover": true
> },
> {
> "name": "test2",
> "url": "http://10.25.133.12:8080/",
> "role": "secondary",
> "auto-failover": true
> }
> ]
> }]
> }
> }
> ]
>
> },
>
>
>
> "Logging": {
> "loggers": [{
> "name": "kea-dhcp4",
> "output_options": [{
> "output": "/var/log/kea-dhcp4.log"
> }],
> "severity": "DEBUG"
> }]
> }
> }
Note: checked firewall, both API able to talk but not able communicate with running dhcp4 daemons.
Both API receives heartbeat :
-agent.commands/29078] COMMAND_RECEIVED Received command 'ha-heartbeat'
2018-10-15 06:29:04.182 INFO [kea-ctrl-agent.commands/29078] COMMAND_RECEIVED Received command 'ha-heartbeat'
2018-10-15 06:29:15.196 INFO [kea-ctrl-agent.commands/29078] COMMAND_RECEIVED Received command 'ha-heartbeat'
anyone could have suggestions ?https://gitlab.isc.org/isc-projects/kea/-/issues/155Kea does not reload hooks correctly on receipt of HUP signal2018-10-17T10:24:25ZThomas MarkwalderKea does not reload hooks correctly on receipt of HUP signalAs reported by: Dave Cole
Software Version: kea-1.3.0, kea-1.4.0
OS: Debian Stretch
Using kill -HUP on the Kea server only correctly reloads hooks if the server has not served any DHCP requests.
If you serve any requests then HUP the s...As reported by: Dave Cole
Software Version: kea-1.3.0, kea-1.4.0
OS: Debian Stretch
Using kill -HUP on the Kea server only correctly reloads hooks if the server has not served any DHCP requests.
If you serve any requests then HUP the server the behaviour is incorrect (and subtly different for 1.3.0 and 1.4.0). In both instances the first HUP after serving requests will load a new instance of the hooks without calling the unload hook. In both instances a subsequent HUP will call the unload hook and then load hook.
Version 1.3.0 and 1.4.0 behave differently during server shutdown. Version 1.3.0 performs the correct number (2) of unloads, but 1.4.0 only calls unload once.
In summary the sequence for 1.3.0 looks like:
load, dhcp, SIGHUP, load, SIGHUP, unload, load, SIGINT, unload, unload, exit.
For 1.4.0 the sequence looks like:
load, dhcp, SIGHUP, load, SIGHUP, unload, load, SIGINT, unload, exit.Thomas MarkwalderThomas Markwalderhttps://gitlab.isc.org/isc-projects/kea/-/issues/172Please add doc for kea HA with load-balancing2018-10-17T11:10:28ZGhost UserPlease add doc for kea HA with load-balancingI know we have :
https://kea.isc.org/wiki/HADesign
for kea HA but in that page load-balancing setup it's doesn't have how exaclty load-balancing works on kea with 50/50 split request handling. I am creating POC with kea but i am unable p...I know we have :
https://kea.isc.org/wiki/HADesign
for kea HA but in that page load-balancing setup it's doesn't have how exaclty load-balancing works on kea with 50/50 split request handling. I am creating POC with kea but i am unable properly understand the load-balacing concept in kea with the documents. It's really good to have more documentation for Kea HA.
In case anyone have already docs or other suggestions. Please share
Thankshttps://gitlab.isc.org/isc-projects/kea/-/issues/127Distribute yang models2018-10-19T09:56:06ZFrancis DupontDistribute yang modelsKea1.5-beta1https://gitlab.isc.org/isc-projects/kea/-/issues/23gitlab HOWTO2018-10-19T11:50:39ZFrancis Dupontgitlab HOWTOThis to discuss gitlab HOWTO. No Kea code expected!
The howto is documented [here](../wikis/gitlab-howto)This to discuss gitlab HOWTO. No Kea code expected!
The howto is documented [here](../wikis/gitlab-howto)Kea1.5-beta1Tomek MrugalskiTomek Mrugalskihttps://gitlab.isc.org/isc-projects/kea/-/issues/148lib process servers without arguments2018-10-19T22:25:15ZFrancis Dupontlib process servers without argumentsAll servers that use CPL architecture (D2, CA, netconf) are unable to print out usage information when run without any parameters. Instead, they print out cryptic error message as shown below:
```$ kea-ctrl-agent
2018-10-01 22:28:51.285...All servers that use CPL architecture (D2, CA, netconf) are unable to print out usage information when run without any parameters. Instead, they print out cryptic error message as shown below:
```$ kea-ctrl-agent
2018-10-01 22:28:51.285 FATAL [kea-ctrl-agent.dctl/23508] DCTL_PID_FILE_ERROR
Control-agent could not create a PID file: Daemon::makePIDFileName config file name is not set
Service failed: Launch failed: Daemon::makePIDFileName config file name is not set'''Kea1.5-beta1https://gitlab.isc.org/isc-projects/kea/-/issues/130Provide sample ('complete') json configuration files with all the keys presen...2018-10-24T13:12:45ZCathy AlmondProvide sample ('complete') json configuration files with all the keys present, demonstrating their usageA Support customer asked (in ticket https://support.isc.org/Ticket/Display.html?id=13388):
```
I would like to have a complete json configuration file with all the "keys" present. Is this something you can help me with?
i have searched...A Support customer asked (in ticket https://support.isc.org/Ticket/Display.html?id=13388):
```
I would like to have a complete json configuration file with all the "keys" present. Is this something you can help me with?
i have searched but not found a complete configuration for kea 1.3 & 1.4
```
The engineering response was to craft a v4 configuration containing all keys or almost all keys. It comes with the following warning:
`Note that this configuration may not be valid, even though it is valid JSON, because usually we don't specify all keys. It is meant to be an example of what parameters can be specified at what level.`
This feature request is to formalise the need for such a document, and to extend it to cover other areas of Kea Configuration, starting with v6, and potentially extending to the control agent.
Meanwhile, here is what was generated for v4:
```
{
"Dhcp4": {
"next-server": "192.0.2.123",
"boot-file-name": "/dev/null",
"client-classes": [
{
"boot-file-name": "",
"name": "phones_server1",
"next-server": "0.0.0.0",
"option-data": [],
"option-def": [],
"server-hostname": "",
"test": "member('HA_server1')"
},
{
"boot-file-name": "",
"name": "phones_server2",
"next-server": "0.0.0.0",
"option-data": [],
"option-def": [],
"server-hostname": "",
"test": "member('HA_server2')"
},
{
"boot-file-name": "",
"name": "laptops_server1",
"next-server": "0.0.0.0",
"option-data": [],
"option-def": [],
"server-hostname": "",
"test": "member('HA_server1')"
},
{
"boot-file-name": "",
"name": "laptops_server2",
"next-server": "0.0.0.0",
"option-data": [],
"option-def": [],
"server-hostname": "",
"test": "member('HA_server2')"
}
],
"control-socket": {
"socket-name": "/tmp/kea-dhcp4-ctrl.sock",
"socket-type": "unix"
},
"decline-probation-period": 86400,
"dhcp-ddns": {
"always-include-fqdn": false,
"enable-updates": false,
"generated-prefix": "myhost",
"hostname-char-replacement": "",
"hostname-char-set": "",
"max-queue-size": 1024,
"ncr-format": "JSON",
"ncr-protocol": "UDP",
"override-client-update": false,
"override-no-update": false,
"qualifying-suffix": "",
"replace-client-name": "never",
"sender-ip": "0.0.0.0",
"sender-port": 0,
"server-ip": "127.0.0.1",
"server-port": 53001
},
"dhcp4o6-port": 0,
"echo-client-id": true,
"expired-leases-processing": {
"flush-reclaimed-timer-wait-time": 25,
"hold-reclaimed-time": 3600,
"max-reclaim-leases": 100,
"max-reclaim-time": 250,
"reclaim-timer-wait-time": 10,
"unwarned-reclaim-cycles": 5
},
"hooks-libraries": [
{
"library": "/home/marcin/devel/kea-build/lib/hooks/libdhcp_lease_cmds.so",
"parameters": {}
},
{
"library": "/home/marcin/devel/kea-build/lib/hooks/libdhcp_ha.so",
"parameters": {
"high-availability": [
{
"heartbeat-delay": 10000,
"max-ack-delay": 5000,
"max-response-delay": 10000,
"max-unacked-clients": 0,
"mode": "load-balancing",
"peers": [
{
"auto-failover": true,
"name": "server1",
"role": "primary",
"url": "http://192.168.56.33:8080/"
},
{
"auto-failover": true,
"name": "server2",
"role": "secondary",
"url": "http://192.168.56.66:8080/"
}
],
"send-lease-updates": true,
"state-machine": {
"states": [
{
"pause": "always",
"state": "waiting"
},
{
"pause": "once",
"state": "partner-down"
}
]
},
"sync-leases": true,
"sync-timeout": 60000,
"this-server-name": "server1"
}
]
}
}
],
"host-reservation-identifiers": [
"hw-address",
"duid",
"circuit-id",
"client-id"
],
"interfaces-config": {
"dhcp-socket-type": "udp",
"interfaces": [
"enp0s8"
],
"re-detect": true
},
"lease-database": {
"lfc-interval": 3600,
"name": "/home/marcin/devel/kea-build/kea-dhcp4.csv",
"persist": true,
"type": "memfile"
},
"option-data": [
{
"always-send": false,
"code": 6,
"csv-format": true,
"data": "192.0.3.1, 192.0.3.2",
"name": "domain-name-servers",
"space": "dhcp4"
}
],
"option-def": [],
"rebind-timer": 40,
"renew-timer": 30,
"sanity-checks": {
"lease-checks": "warn"
},
"shared-networks": [
{
"match-client-id": true,
"name": "my-secret-network",
"option-data": [],
"relay": {
"ip-addresses": []
},
"reservation-mode": "all",
"require-client-classes": [ "Client_foo" ],
"subnet4": [
{
"4o6-interface": "",
"4o6-interface-id": "",
"4o6-subnet": "",
"boot-file-name": "",
"id": 1,
"match-client-id": true,
"next-server": "0.0.0.0",
"option-data": [
{
"always-send": false,
"code": 3,
"csv-format": true,
"data": "192.0.3.1",
"name": "routers",
"space": "dhcp4"
}
],
"pools": [
{
"client-class": "phones_server1",
"option-data": [],
"pool": "192.1.0.1/16"
},
{
"client-class": "laptops_server1",
"option-data": [],
"pool": "192.2.0.1/16"
},
{
"client-class": "phones_server2",
"option-data": [],
"pool": "192.3.0.1/16"
},
{
"client-class": "laptops_server2",
"option-data": [],
"pool": "192.4.0.1/16"
}
],
"rebind-timer": 40,
"relay": {
"ip-addresses": [
"192.168.56.1"
]
},
"renew-timer": 30,
"reservation-mode": "all",
"reservations": [],
"require-client-classes": [ "Client_foo" ],
"server-hostname": "",
"subnet": "192.0.0.0/8",
"valid-lifetime": 6000
}
]
}
],
"subnet4": [],
"valid-lifetime": 6000
},
"Logging": {
"loggers": [
{
"debuglevel": 99,
"name": "kea-dhcp4",
"output_options": [
{
"flush": true,
"maxsize": 10240000,
"maxver": 1,
"output": "stdout"
}
],
"severity": "INFO"
},
{
"debuglevel": 99,
"name": "kea-dhcp4.ha_hooks",
"output_options": [
{
"flush": true,
"maxsize": 10240000,
"maxver": 1,
"output": "stdout"
}
],
"severity": "INFO"
},
{
"debuglevel": 99,
"name": "kea-dhcp4.commands",
"output_options": [
{
"flush": true,
"maxsize": 10240000,
"maxver": 1,
"output": "stdout"
}
],
"severity": "INFO"
},
{
"debuglevel": 99,
"name": "kea-dhcp4.http",
"output_options": [
{
"flush": true,
"maxsize": 10240000,
"maxver": 1,
"output": "stdout"
}
],
"severity": "INFO"
}
]
}
}
```Kea1.5-beta2Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/kea/-/issues/187leases database declaration is missing from yang models2018-10-24T21:36:15ZWlodzimierz Wencelleases database declaration is missing from yang models.....invalid.....invalidhttps://gitlab.isc.org/isc-projects/kea/-/issues/197global host reservations example2018-10-30T11:30:28ZTomek Mrugalskiglobal host reservations exampleWe need to update examples do doc/examples with global reservation mechanisms. Yes, it's already explained in the User's Guide, but there are two reasons to also have the examples updated. First, some people don't read the docs. Second, ...We need to update examples do doc/examples with global reservation mechanisms. Yes, it's already explained in the User's Guide, but there are two reasons to also have the examples updated. First, some people don't read the docs. Second, we use examples in unit-tests, so they could potentially uncover problems.Kea1.5-beta2Tomek MrugalskiTomek Mrugalskihttps://gitlab.isc.org/isc-projects/kea/-/issues/93CB: Implement MySQLConfigBackendDHCPv4 class2018-10-30T15:53:39ZMarcin SiodelskiCB: Implement MySQLConfigBackendDHCPv4 classThe MySQLConfigBackend class implements Config Backend for MySQL as described in https://gitlab.isc.org/isc-projects/kea/wikis/designs/configuration-in-db-designThe MySQLConfigBackend class implements Config Backend for MySQL as described in https://gitlab.isc.org/isc-projects/kea/wikis/designs/configuration-in-db-designKea1.5-beta1Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/kea/-/issues/194libkea-process unnecessarily links with MySQL, PgSQL and CQL2018-11-01T10:35:39ZMarcin Siodelskilibkea-process unnecessarily links with MySQL, PgSQL and CQLPreviously, libkea-process depended on libkea-dhcpsrv. Therefore, it had to conditionally link with MySQL and co. After we reversed the dependency, so as the libkea-dhcpsrv now depends on libkea-process, linking with MySQL is no longer n...Previously, libkea-process depended on libkea-dhcpsrv. Therefore, it had to conditionally link with MySQL and co. After we reversed the dependency, so as the libkea-dhcpsrv now depends on libkea-process, linking with MySQL is no longer needed.Kea1.5-beta1Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/kea/-/issues/180Address some doxygen warnings / errors2018-11-05T08:06:52ZFrancis DupontAddress some doxygen warnings / errorsKea1.5-beta2https://gitlab.isc.org/isc-projects/kea/-/issues/65library for yang <-> json configuration element translators2018-11-05T09:44:05ZGhost Userlibrary for yang <-> json configuration element translatorsNew library with yang <-> json translators for representation of configuration elements.
A priori one fro `src/lib/dhcpsrv/parsers` parse class.New library with yang <-> json translators for representation of configuration elements.
A priori one fro `src/lib/dhcpsrv/parsers` parse class.Kea1.5-beta1Francis DupontFrancis Dupont