5 commits

Author	SHA1	Message	Date
Madhu Venugopal	03504cab65	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 21:57:18 -07:00
Madhu Venugopal	613e60bcec	support for libnetwork daemon labels ... Signed-off-by: Madhu Venugopal <madhu@docker.com>	2015-06-14 09:03:42 -07:00
Madhu Venugopal	9f3d1ce3ff	Moved the TOML based Configuration to dnet ... The configuration format for docker runtime is based on daemon flags and hence adjusting the libnetwork configuration to accomodate it by moving the TOML based configuration to the dnet tool. Also changed the controller configuration via options Signed-off-by: Madhu Venugopal <madhu@docker.com>	2015-06-12 12:46:12 -07:00
Madhu Venugopal	ae8643748d	Libnetwork Host Discovery using Swarm Discovery pkg ... Signed-off-by: Madhu Venugopal <madhu@docker.com>	2015-05-25 16:29:40 -07:00
Madhu Venugopal	481568035f	TOML based Configuration support for libnetwork ... Signed-off-by: Madhu Venugopal <madhu@docker.com>	2015-05-25 16:29:40 -07:00