mir/kea
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/kea synced 2025-08-30 05:27:55 +00:00
Code Issues Releases Wiki Activity

Update kea multithreading packet processing requirements

Razvan Becheriu 2019-09-13 12:36:45 -04:00
parent e8ea5b7f48
commit d39e7ec5d1
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
kea-multithreading-packet-processing-requirements.md

@ -3,13 +3,13 @@
# The initial requirements of the kea multi-threading packet processing design:
1. It must be supported by DHCPv4 and DHCPv6 servers
* 2 It must not break the DHCP protocol (obviously)
* 3 It must compile and use supported dependencies on all supported platforms (obviously)
* 4 It must be configurable in the configuration file, at run-time using control channel commands or on the command line (still in discussion).
* 5 Should not have impact on the old server functionality if the feature is disabled
* 6 It must support MySql and PgSql back-ends
* 7 It must support Memfile and Cassandra back-ends (initial implementation might disable the feature or use a hybrid approach if configured with these back-ends)
* 8 It must support using hooks (some, all or none) (initial implementation might disable the feature or use a hybrid approach if configured with unsupported hooks)
2. It must not break the DHCP protocol (obviously)
3. It must compile and use supported dependencies on all supported platforms (obviously)
4. It must be configurable in the configuration file, at run-time using control channel commands or on the command line (still in discussion).
5. Should not have impact on the old server functionality if the feature is disabled
6. It must support MySql and PgSql back-ends
7. It must support Memfile and Cassandra back-ends (initial implementation might disable the feature or use a hybrid approach if configured with these back-ends)
8. It must support using hooks (some, all or none) (initial implementation might disable the feature or use a hybrid approach if configured with unsupported hooks)
***As the development goes further and the design is perfected, these requirements must be updated.***