Provide basic configuration templates for sample use cases

We have a number of example configurations in a separate file in the Kea distribution. These show how to use different features of Kea. The problem is, a new user is looking for a template to cut and paste to start with.

What we would like is to add example configurations that a user will recognize as 'probably fits my needs', and document these in the ARM. The example configuration descriptions should include what we are assuming the requirements are for that scenario, what lease lifetimes, traffic levels and so on we expect, and what hardware/sw we suggest. If we can import the configurations into the ARM, great, or we else we can link to the json files. Then we can refer them to the existing examples for how to add the xyz feature, if their scenario requires that and we didn't include it.

These example configurations could be included as an appendix to the ARM or in the Getting Started section.

We might want a handful of these eventually, starting with the simplest and most common.

• power home user - 256 addresses, dhcpv4 or ipv6 pd, wants failover with v. inexpensive hw, minimal traffic, no dbs. !1418 (merged)

• small organization - several small dhcpv4 subnets, 20 host reservations, failover, memfile, guest wifi plus 'internal' users. Low traffic Maybe we could model this on the old ISC hq?

• multi-site enterprise - DHCPv4 and DHCPv6. multiple clusters each serving local geography. 100s of host reservations, 1000s of clients, failover (within a site), separate guest network/wifi, possibly captive portal to register?)

• hub and spokes enterprise, such as retail (dozens to hundreds of locations with local failover, centralized configuration mgmt, likely dhcpv4 only legacy devices with odd vendor options....).

• small wired service provider (1-3 data centers, <100K subs, v4 and v6 w/pd, failover, multi-threading, forensic logging, classification for premium, known and unknown users, home gateways with RFC 1918, 3-4 addresses per gw. e.g. small municipal fiber provider

• large wired service provider (>3 data centers, >100K subs, v4 and v6 with pd, config backend. Some ability to identify premium users. e.g. Cable access provider, cable modems.

• wireless service provider (not sure how this is different, except perhaps much shorter lease times, higher traffic for the same number of users, more likely to be v6? highest performance configuration, captive portal)