... | ... | @@ -92,7 +92,7 @@ Here's an outline of a functional test: |
|
|
|
|
|
1. Start kea-dhcp4 with a minimal configuration that has only unix socket in it. This is explained in the [Kea user's guide, section 20.6](https://jenkins.isc.org/job/Kea_doc/guide/kea-guide.html#kea-netconf).
|
|
|
|
|
|
1. Start kea-netconf with appropriate configuration. It must at least have the managed-servers entry with dhcp4 in it. It should point to the unix socket that was configured in kea-dhcp4 configuration. Once started, it should retrieve the whole configration from sysrepo and send config-set over to kea-dhcp4.
|
|
|
1. Start kea-netconf with appropriate configuration. It must at least have the managed-servers entry with dhcp4 in it. It should point to the unix socket that was configured in kea-dhcp4 configuration. Once started, it should retrieve the whole configuration from sysrepo and send config-set over to kea-dhcp4.
|
|
|
|
|
|
There are many aspects to consider here. the kea-netconf can be told to send the commands to stdout rather to unix socket. This has little practical value, but can be super helpful in testing. It will allow us to investigate whether the netconf sent correct or invalid config-set.
|
|
|
|
... | ... | |