cassandra.json 2.0 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364
  1. // This is an example configuration file for the DHCPv4 server in Kea.
  2. // It is a basic scenario with one IPv4 subnet configured. It demonstrates
  3. // how to configure Kea to use CQL (Cassandra) backend
  4. { "Dhcp4":
  5. {
  6. // Kea is told to listen on ethX interface only.
  7. "interfaces-config": {
  8. "interfaces": [ "ethX" ]
  9. },
  10. // 4. CQL (Cassandra) backend. Leases will be stored in Cassandra database. Make
  11. // sure it is up, running and properly initialized. See kea-admin documentation
  12. // for details on how to initialize the database. The only strictly required
  13. // parameters are type, keyspace and contact-points. At least one contact point
  14. // must be specified, but more than one is required for redundancy. Make sure
  15. // you specify the contact points without spaces. Kea must be compiled with
  16. // --with-cql option to use this backend.
  17. "lease-database": {
  18. "type": "cql",
  19. "keyspace": "keatest",
  20. "contact-points": "192.0.2.1,192.0.2.2,192.0.2.3",
  21. "port": 9042
  22. },
  23. // Addresses will be assigned with a lifetime of 4000 seconds.
  24. "valid-lifetime": 4000,
  25. // Renew and rebind timers are commented out. This implies that options
  26. // 58 and 59 will not be sent to the client. In this case it is up to
  27. // the client to pick the timer values according to RFC2131. Uncomment the
  28. // timers to send these options to the client.
  29. // "renew-timer": 1000,
  30. // "rebind-timer": 2000,
  31. // The following list defines subnets. We have only one subnet
  32. // here. We tell Kea that it is directly available over local interface.
  33. "subnet4": [
  34. {
  35. "pools": [ { "pool": "192.0.2.1 - 192.0.2.200" } ],
  36. "subnet": "192.0.2.0/24",
  37. "interface": "ethX"
  38. }
  39. ]
  40. },
  41. // The following configures logging. It assumes that messages with at least
  42. // informational level (info, warn, error and fatal) should be logged to stdout.
  43. "Logging": {
  44. "loggers": [
  45. {
  46. "name": "kea-dhcp4",
  47. "output_options": [
  48. {
  49. "output": "stdout"
  50. }
  51. ],
  52. "severity": "INFO"
  53. }
  54. ]
  55. }
  56. }