4 commits

Author	SHA1	Message	Date
David Calavera	cc02894a50	Move test specific functions to a testutils package. ... This way we won't vendor test related functions in docker anymore. It also moves netns related functions to a new ns package to be able to call the ns init function in tests. I think this also helps with the overall package isolation. Signed-off-by: David Calavera <david.calavera@gmail.com>	2015-09-07 13:33:28 -04:00
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
Alessandro Boch	7de9f71eb5	Promote Service cli ... - To the same level of Network cli and to make use of the new service rest apis Signed-off-by: Alessandro Boch <aboch@docker.com>	2015-06-11 16:07:09 -07:00
Madhu Venugopal	a0cccbbcfa	Moved services to dnet top-level and removed experimental ... In prep for the UI/API updates on Docker to integrate the network and endpoints, this PR removes the experimental tag from dnet and moving it to docker UI and API and wrap the top-level "network" and "service" under experimental. Signed-off-by: Madhu Venugopal <madhu@docker.com>	2015-06-08 14:23:41 -07:00

Renamed from libnetwork/client/client_experimental_test.go (Browse further)