kotovalexarian-likes-github/moby--moby
1
0
Fork 0
mirror of https://github.com/moby/moby.git synced 2022-11-09 12:21:53 -05:00
Code Releases Activity
moby--moby/libnetwork/cmd/dnet/libnetwork.toml

17 lines
304 B
TOML
Raw Normal View History

Few changes to the UI and API implementation 1. replaced --net option for service UI with SERVICE.[NETWORK] format 2. Making using of the default network/driver backend support 3. NetworkName and NetworkType from the UI/API can be empty string and it will be replaced with DefaultNetwork and DefaultDriver As per the design goals, we wanted to keep libnetwork core free of handling defaults. Rather, the clients (docker & dnet) must handle the defaultness of these entities. Also, since there is no API to get these Default values from the backend, UI will not handle the default values either. Hence, this falls under the responsibility of the API layer to handle this specific case. Signed-off-by: Madhu Venugopal <madhu@docker.com>
2015-06-14 12:00:27 -04:00
title = "LibNetwork Configuration file"
[daemon]
debug = false
[cluster]
Integration with Docker Discovery * integrated hostdiscovery package with the new Docker Discovery * Integrated hostdiscovery package with libnetwork core * removed libnetwork_discovery tag * Introduced driver apis for discovery events * moved overlay driver to make use of the discovery events * Using Docker Discovery service. * Changed integration-tests to make use of the new discovery Signed-off-by: Madhu Venugopal <madhu@docker.com>
2015-09-18 15:54:08 -04:00
discovery = "consul://localhost:8500"
Few changes to the UI and API implementation 1. replaced --net option for service UI with SERVICE.[NETWORK] format 2. Making using of the default network/driver backend support 3. NetworkName and NetworkType from the UI/API can be empty string and it will be replaced with DefaultNetwork and DefaultDriver As per the design goals, we wanted to keep libnetwork core free of handling defaults. Rather, the clients (docker & dnet) must handle the defaultness of these entities. Also, since there is no API to get these Default values from the backend, UI will not handle the default values either. Hence, this falls under the responsibility of the API layer to handle this specific case. Signed-off-by: Madhu Venugopal <madhu@docker.com>
2015-06-14 12:00:27 -04:00
Address = "1.1.1.1"
Integration with Docker Discovery * integrated hostdiscovery package with the new Docker Discovery * Integrated hostdiscovery package with libnetwork core * removed libnetwork_discovery tag * Introduced driver apis for discovery events * moved overlay driver to make use of the discovery events * Using Docker Discovery service. * Changed integration-tests to make use of the new discovery Signed-off-by: Madhu Venugopal <madhu@docker.com>
2015-09-18 15:54:08 -04:00
Heartbeat = 20
Few changes to the UI and API implementation 1. replaced --net option for service UI with SERVICE.[NETWORK] format 2. Making using of the default network/driver backend support 3. NetworkName and NetworkType from the UI/API can be empty string and it will be replaced with DefaultNetwork and DefaultDriver As per the design goals, we wanted to keep libnetwork core free of handling defaults. Rather, the clients (docker & dnet) must handle the defaultness of these entities. Also, since there is no API to get these Default values from the backend, UI will not handle the default values either. Hence, this falls under the responsibility of the API layer to handle this specific case. Signed-off-by: Madhu Venugopal <madhu@docker.com>
2015-06-14 12:00:27 -04:00
[datastore]
embedded = false
Reading the top level element (network) from datastore on init Currently we rely on watch to catchup after the init. But there could be a small time window on which, we might end up in a race condition on network creates. By reading and populating networks during init, we avoid any such conditions, especially for default network handling. Signed-off-by: Madhu Venugopal <madhu@docker.com>
2015-06-18 11:18:17 -04:00
[datastore.client]
provider = "consul"
Address = "localhost:8500"
Provide a way for libnetwork to make use of Agent mode functionalities Signed-off-by: Madhu Venugopal <madhu@docker.com>
2016-05-24 19:17:19 -04:00
[orchestration]
agent = true
peer="2.2.2.2"
Copy permalink