|
|
This page attempts to capture what are the potential design boundaries for Stork.
|
|
|
|
|
|
- max number of subnets in kea: 13k
|
|
|
- max number of Kea HA pairs: 100 (although 18k was discussed in one deployment)
|
|
|
- max number of reservations: ?
|
|
|
- max number of BIND servers: 500
|
|
|
- max number of zones: 1M
|
|
|
- max number of records in a zone: 1M
|
|
|
- max number of leases: 2M (although this may be increased to 20M soon)
|
|
|
| max number of | stork limit | max seen in real life |
|
|
|
| -- | -- | -- |
|
|
|
| subnets in kea | | 13k |
|
|
|
| Kea HA pairs | | 100 (although 18k was discussed in one deployment) |
|
|
|
| reservations | | ? |
|
|
|
| BIND servers | | 500 |
|
|
|
| zones | | 1M |
|
|
|
| records in a zone | | 1M |
|
|
|
| leases | | 2M (although this may be increased to 20M soon) |
|
|
|
|
|
|
If your deployment is bigger than this, Stork will not magically refuse to work. You will simply be using it outside of its design boundaries. This most likely be manifested by some aspects may be unreasonably slow or time out etc. Please contact ISC if you'd like to discuss how we can extend Stork to cover your deployment. |
|
|
\ No newline at end of file |