Commit 05072326 authored by Marcin Siodelski's avatar Marcin Siodelski

[3684] Updated examples as a result of review.

parent 0aeb76d8
......@@ -68,11 +68,7 @@
# "contact_points": "192.0.2.1,192.0.2.2,192.0.2.3"
# },
# Addresses will be assigned with valid lifetimes being 4000. Client
# is told to start renewing after 1000 seconds. If the server does not respond
# after 2000 seconds since the lease was granted, client is supposed
# to start REBIND procedure (emergency renewal that allows switching
# to a different server).
# Addresses will be assigned with valid lifetimes being 4000.
"valid-lifetime": 4000,
# Renew and rebind timers are commented out. This implies that options
......
......@@ -10,9 +10,10 @@
"interfaces": [ "ethX" ]
},
# We need to specify lease type. As of May 2014, three backends are supported:
# memfile, mysql and pgsql. We'll just use memfile, because it doesn't require
# any prior set up.
# We need to specify the the database used to store leases. As of
# September 2016, four database backends are supported: MySQL,
# PostgreSQL, Cassandra, and the in-memory database, Memfile.
# We'll use memfile because it doesn't require any prior set up.
"lease-database": {
"type": "memfile"
},
......@@ -34,11 +35,7 @@
"unwarned-reclaim-cycles": 10
},
# Addresses will be assigned with valid lifetimes being 4000. Client
# is told to start renewing after 1000 seconds. If the server does not respond
# after 2000 seconds since the lease was granted, client is supposed
# to start REBIND procedure (emergency renewal that allows switching
# to a different server).
# Addresses will be assigned with valid lifetimes being 4000.
"valid-lifetime": 4000,
# The following list defines subnets. We have only one subnet
......
......@@ -9,18 +9,15 @@
"interfaces": [ "ethX" ]
},
# We need to specify lease type. As of May 2014, three backends are supported:
# memfile, mysql and pgsql. We'll just use memfile, because it doesn't require
# any prior set up.
# We need to specify the the database used to store leases. As of
# September 2016, four database backends are supported: MySQL,
# PostgreSQL, Cassandra, and the in-memory database, Memfile.
# We'll use memfile because it doesn't require any prior set up.
"lease-database": {
"type": "memfile"
},
# Addresses will be assigned with valid lifetimes being 4000. Client
# is told to start renewing after 1000 seconds. If the server does not respond
# after 2000 seconds since the lease was granted, client is supposed
# to start REBIND procedure (emergency renewal that allows switching
# to a different server).
# Addresses will be assigned with valid lifetimes being 4000.
"valid-lifetime": 4000,
# Renew and rebind timers are commented out. This implies that options
......
......@@ -8,20 +8,18 @@
# Kea is told to listen on ethX interface only.
"interfaces-config": {
"interfaces": [ "ethX" ]
},
# We need to specify lease type. As of May 2014, three backends are supported:
# memfile, mysql and pgsql. We'll just use memfile, because it doesn't require
# any prior set up.
# We need to specify the the database used to store leases. As of
# September 2016, four database backends are supported: MySQL,
# PostgreSQL, Cassandra, and the in-memory database, Memfile.
# We'll use memfile because it doesn't require any prior set up.
"lease-database": {
"type": "memfile"
},
# Addresses will be assigned with valid lifetimes being 4000. Client
# is told to start renewing after 1000 seconds. If the server does not respond
# after 2000 seconds since the lease was granted, client is supposed
# to start REBIND procedure (emergency renewal that allows switching
# to a different server).
# Addresses will be assigned with valid lifetimes being 4000.
"valid-lifetime": 4000,
# Renew and rebind timers are commented out. This implies that options
......
......@@ -10,18 +10,16 @@
"interfaces": [ "ethX" ]
},
# We need to specify lease type. As of May 2014, three backends are supported:
# memfile, mysql and pgsql. We'll just use memfile, because it doesn't require
# any prior set up.
# We need to specify the the database used to store leases. As of
# September 2016, four database backends are supported: MySQL,
# PostgreSQL, Cassandra, and the in-memory database, Memfile.
# We'll use memfile because it doesn't require any prior set up.
"lease-database": {
"type": "memfile"
},
# Addresses will be assigned with valid lifetimes being 4000. Client
# is told to start renewing after 1000 seconds. If the server does not respond
# after 2000 seconds since the lease was granted, client is supposed
# to start REBIND procedure (emergency renewal that allows switching
# to a different server).
# Addresses will be assigned with valid lifetimes being 4000.
"valid-lifetime": 4000,
# Renew and rebind timers are commented out. This implies that options
......
......@@ -9,18 +9,15 @@
"interfaces": [ "ethX" ]
},
# We need to specify lease type. As of May 2014, three backends are supported:
# memfile, mysql and pgsql. We'll just use memfile, because it doesn't require
# any prior set up.
# We need to specify the the database used to store leases. As of
# September 2016, four database backends are supported: MySQL,
# PostgreSQL, Cassandra, and the in-memory database, Memfile.
# We'll use memfile because it doesn't require any prior set up.
"lease-database": {
"type": "memfile"
},
# Addresses will be assigned with valid lifetimes being 4000. Client
# is told to start renewing after 1000 seconds. If the server does not respond
# after 2000 seconds since the lease was granted, client is supposed
# to start REBIND procedure (emergency renewal that allows switching
# to a different server).
# Addresses will be assigned with valid lifetimes being 4000.
"valid-lifetime": 4000,
# Renew and rebind timers are commented out. This implies that options
......
......@@ -10,9 +10,10 @@
"interfaces": [ "ethX" ]
},
# We need to specify lease type. As of May 2014, three backends are supported:
# memfile, mysql and pgsql. We'll just use memfile, because it doesn't require
# any prior set up.
# We need to specify the the database used to store leases. As of
# September 2016, four database backends are supported: MySQL,
# PostgreSQL, Cassandra, and the in-memory database, Memfile.
# We'll use memfile because it doesn't require any prior set up.
"lease-database": {
"type": "memfile"
},
......@@ -37,19 +38,18 @@
"subnet": "192.0.4.0/24" } ]
},
# The following configures logging. Kea will log all debug messages
# to /var/log/kea-debug.log file.
# The following configures logging. It assumes that messages with at least
# informational level (info, warn, error) will will be logged to stdout.
"Logging": {
"loggers": [
{
"name": "kea-dhcp4",
"output_options": [
{
"output": "/var/log/kea-debug.log"
"output": "stdout"
}
],
"debuglevel": 99,
"severity": "DEBUG"
"severity": "INFO"
}
]
}
......
......@@ -10,18 +10,15 @@
"interfaces": [ "ethX" ]
},
# We need to specify lease type. As of May 2014, three backends are supported:
# memfile, mysql and pgsql. We'll just use memfile, because it doesn't require
# any prior set up.
# We need to specify the the database used to store leases. As of
# September 2016, four database backends are supported: MySQL,
# PostgreSQL, Cassandra, and the in-memory database, Memfile.
# We'll use memfile because it doesn't require any prior set up.
"lease-database": {
"type": "memfile"
},
# Addresses will be assigned with valid lifetimes being 4000. Client
# is told to start renewing after 1000 seconds. If the server does not respond
# after 2000 seconds since the lease was granted, client is supposed
# to start REBIND procedure (emergency renewal that allows switching
# to a different server).
# Addresses will be assigned with valid lifetimes being 4000.
"valid-lifetime": 4000,
# Renew and rebind timers are commented out. This implies that options
......
......@@ -15,9 +15,10 @@
"interfaces": [ "ethX" ]
},
# We need to specify lease type. As of May 2014, three backends are supported:
# memfile, mysql and pgsql. We'll just use memfile, because it doesn't require
# any prior set up.
# We need to specify the the database used to store leases. As of
# September 2016, four database backends are supported: MySQL,
# PostgreSQL, Cassandra, and the in-memory database, Memfile.
# We'll use memfile because it doesn't require any prior set up.
"lease-database": {
"type": "memfile"
},
......@@ -71,19 +72,19 @@
]
},
# The following configures logging. Kea will log all debug messages
# to /var/log/kea-debug.log file.
# The following configures logging. It assumes that messages with at least
# informational level (info, warn, error) will will be logged to stdout.
"Logging": {
"loggers": [
{
"name": "kea-dhcp6",
"output_options": [
{
"output": "/var/log/kea-debug.log"
"output": "stdout"
}
],
"debuglevel": 99,
"severity": "DEBUG"
"debuglevel": 0,
"severity": "INFO"
}
]
}
......
......@@ -90,15 +90,15 @@
]
},
# The following configures logging. Kea will log all debug messages
# to /var/log/kea-debug.log file.
# The following configures logging. It assumes that messages with at least
# informational level (info, warn, error) will will be logged to stdout.
"Logging": {
"loggers": [
{
"name": "kea-dhcp6",
"output_options": [
{
"output": "/var/log/kea-debug.log"
"output": "stdout"
}
],
"debuglevel": 0,
......
......@@ -66,19 +66,19 @@
]
},
# The following configures logging. Kea will log all debug messages
# to /var/log/kea-debug.log file.
# The following configures logging. It assumes that messages with at least
# informational level (info, warn, error) will will be logged to stdout.
"Logging": {
"loggers": [
{
"name": "kea-dhcp6",
"output_options": [
{
"output": "/var/log/kea-debug.log"
"output": "stdout"
}
],
"debuglevel": 99,
"severity": "DEBUG"
],
"debuglevel": 0,
"severity": "INFO"
}
]
}
......
......@@ -30,9 +30,10 @@
"interfaces": [ "ethX" ]
},
# We need to specify lease type. As of May 2014, three backends are supported:
# memfile, mysql and pgsql. We'll just use memfile, because it doesn't require
# any prior set up.
# We need to specify the the database used to store leases. As of
# September 2016, four database backends are supported: MySQL,
# PostgreSQL, Cassandra, and the in-memory database, Memfile.
# We'll use memfile because it doesn't require any prior set up.
"lease-database": {
"type": "memfile"
},
......@@ -50,7 +51,7 @@
# The following list defines subnets. Each subnet consists of at
# least subnet and pool entries.
"subnet6": [
"subnet6": [
{
"pools": [ { "pool": "2001:db8:1::/80" } ],
"subnet": "2001:db8:1::/64",
......@@ -59,17 +60,17 @@
]
},
# The following configures logging. Kea will log all debug messages
# to /var/log/kea-debug.log file.
# The following configures logging. It assumes that messages with at least
# informational level (info, warn, error) will will be logged to stdout.
"Logging": {
"loggers": [
{
"name": "kea-dhcp6",
"output_options": [
{
"output": "/var/log/kea-debug.log"
"output": "stdout"
}
],
],
"debuglevel": 0,
"severity": "INFO"
}
......
......@@ -10,9 +10,10 @@
"interfaces": [ "ethX" ]
},
# We need to specify lease type. As of May 2014, three backends are supported:
# memfile, mysql and pgsql. We'll just use memfile, because it doesn't require
# any prior set up.
# We need to specify the the database used to store leases. As of
# September 2016, four database backends are supported: MySQL,
# PostgreSQL, Cassandra, and the in-memory database, Memfile.
# We'll use memfile because it doesn't require any prior set up.
"lease-database": {
"type": "memfile"
},
......@@ -56,19 +57,19 @@
]
},
# The following configures logging. Kea will log all debug messages
# to /var/log/kea-debug.log file.
# The following configures logging. It assumes that messages with at least
# informational level (info, warn, error) will will be logged to stdout.
"Logging": {
"loggers": [
{
"name": "kea-dhcp6",
"output_options": [
{
"output": "/var/log/kea-debug.log"
"output": "stdout"
}
],
"debuglevel": 99,
"severity": "DEBUG"
"debuglevel": 0,
"severity": "INFO"
}
]
}
......
......@@ -9,9 +9,10 @@
"interfaces": [ "ethX" ]
},
# We need to specify lease type. As of May 2014, three backends are supported:
# memfile, mysql and pgsql. We'll just use memfile, because it doesn't require
# any prior set up.
# We need to specify the the database used to store leases. As of
# September 2016, four database backends are supported: MySQL,
# PostgreSQL, Cassandra, and the in-memory database, Memfile.
# We'll use memfile because it doesn't require any prior set up.
"lease-database": {
"type": "memfile"
},
......@@ -49,19 +50,19 @@
]
},
# The following configures logging. Kea will log all debug messages
# to /var/log/kea-debug.log file.
# The following configures logging. It assumes that messages with at least
# informational level (info, warn, error) will will be logged to stdout.
"Logging": {
"loggers": [
{
"name": "kea-dhcp6",
"output_options": [
{
"output": "/var/log/kea-debug.log"
"output": "stdout"
}
],
"debuglevel": 99,
"severity": "DEBUG"
"debuglevel": 0,
"severity": "INFO"
}
]
}
......
......@@ -10,9 +10,10 @@
"interfaces": [ "ethX" ]
},
# We need to specify lease type. As of May 2014, three backends are supported:
# memfile, mysql and pgsql. We'll just use memfile, because it doesn't require
# any prior set up.
# We need to specify the the database used to store leases. As of
# September 2016, four database backends are supported: MySQL,
# PostgreSQL, Cassandra, and the in-memory database, Memfile.
# We'll use memfile because it doesn't require any prior set up.
"lease-database": {
"type": "memfile"
},
......@@ -71,19 +72,19 @@
]
},
# The following configures logging. Kea will log all debug messages
# to /var/log/kea-debug.log file.
# The following configures logging. It assumes that messages with at least
# informational level (info, warn, error) will will be logged to stdout.
"Logging": {
"loggers": [
{
"name": "kea-dhcp6",
"output_options": [
{
"output": "/var/log/kea-debug.log"
"output": "stdout"
}
],
"debuglevel": 99,
"severity": "DEBUG"
"debuglevel": 0,
"severity": "INFO"
}
]
}
......
......@@ -10,9 +10,10 @@
"interfaces": [ "ethX" ]
},
# We need to specify lease type. As of May 2014, three backends are supported:
# memfile, mysql and pgsql. We'll just use memfile, because it doesn't require
# any prior set up.
# We need to specify the the database used to store leases. As of
# September 2016, four database backends are supported: MySQL,
# PostgreSQL, Cassandra, and the in-memory database, Memfile.
# We'll use memfile because it doesn't require any prior set up.
"lease-database": {
"type": "memfile"
},
......@@ -71,19 +72,19 @@
]
},
# The following configures logging. Kea will log all debug messages
# to /var/log/kea-debug.log file.
# The following configures logging. It assumes that messages with at least
# informational level (info, warn, error) will will be logged to stdout.
"Logging": {
"loggers": [
{
"name": "kea-dhcp6",
"output_options": [
{
"output": "/var/log/kea-debug.log"
"output": "stdout"
}
],
"debuglevel": 99,
"severity": "DEBUG"
"debuglevel": 0,
"severity": "INFO"
}
]
}
......
......@@ -12,9 +12,10 @@
"interfaces": [ "ethX" ]
},
# We need to specify lease type. As of May 2014, three backends are supported:
# memfile, mysql and pgsql. We'll just use memfile, because it doesn't require
# any prior set up.
# We need to specify the the database used to store leases. As of
# September 2016, four database backends are supported: MySQL,
# PostgreSQL, Cassandra, and the in-memory database, Memfile.
# We'll use memfile because it doesn't require any prior set up.
"lease-database": {
"type": "memfile"
},
......@@ -109,19 +110,19 @@
]
},
# The following configures logging. Kea will log all debug messages
# to /var/log/kea-debug.log file.
# The following configures logging. It assumes that messages with at least
# informational level (info, warn, error) will will be logged to stdout.
"Logging": {
"loggers": [
{
"name": "kea-dhcp6",
"output_options": [
{
"output": "/var/log/kea-debug.log"
"output": "stdout"
}
],
"debuglevel": 99,
"severity": "DEBUG"
"debuglevel": 0,
"severity": "INFO"
}
]
}
......
......@@ -10,9 +10,10 @@
"interfaces": [ "ethX" ]
},
# We need to specify lease type. As of May 2014, three backends are supported:
# memfile, mysql and pgsql. We'll just use memfile, because it doesn't require
# any prior set up.
# We need to specify the the database used to store leases. As of
# September 2016, four database backends are supported: MySQL,
# PostgreSQL, Cassandra, and the in-memory database, Memfile.
# We'll use memfile because it doesn't require any prior set up.
"lease-database": {
"type": "memfile"
},
......@@ -30,19 +31,19 @@
# The following list defines subnets. Each subnet consists of at
# least subnet and pool entries.
"subnet6": [
"subnet6": [
{ "pools": [ { "pool": "2001:db8:1::/80" } ],
"subnet": "2001:db8:1::/64" },
{ "pools": [ { "pool": "2001:db8:2::/80" } ],
"subnet": "2001:db8:2::/64" },
"subnet": "2001:db8:2::/64" },
{ "pools": [ { "pool": "2001:db8:3::/80" } ],
"subnet": "2001:db8:3::/64" },
{ "pools": [ { "pool": "2001:db8:4::/80" } ],
"subnet": "2001:db8:4::/64" } ]
},
# The following configures logging. It assumes that warning messages
# will be logged to stdout.
# The following configures logging. It assumes that messages with at least
# informational level (info, warn, error) will will be logged to stdout.
"Logging": {
"loggers": [
{
......@@ -52,7 +53,8 @@
"output": "stdout"
}
],
"severity": "WARN"
"debuglevel": 0,
"severity": "INFO"
}
]