client side of NetworkInterfaceWatcher
Merge remote-tracking branch 'upstream/master' into 121-networkinterfaceswatcher
change StringsWatcher to NotifyWatcher
Merge remote-tracking branch 'upstream/master' into 121-networkinterfaceswatcher
Merge remote-tracking branch 'upstream/master' into 121-networkinterfaceswatcher
Merge remote-tracking branch 'upstream/master' into 121-networkinterfaceswatcher
Reaplaced os.Symlink and os.Readlink

symlinks are not supported by standard go os package on windows. Replaced all instances of os.Symlink and os.Readlink with the implementation in github.com/juju/utils/symlink. On linux these functions simply call os.Symlink and os.Readlink. On windows they use our implementation
provider/azure: use affinity group in vnet site

Revert change based on observations of vnet
related issues. Azure console displays advisory
warning about vnets tied to locations, suggesting
vnets be tied to affinity groups to mitigate.
Add link to docs
Merge remote-tracking branch 'upstream/master' into 121-networkinterfaceswatcher
WatchInterfaces for API server
State -> BackingState
restore state test
drop test in apiserver
Merge remote-tracking branch 'upstream/master' into 121-networkinterfaceswatcher
Added two more tests for multiple and no endpoints.
Merge remote-tracking branch 'upstream/master' into 121-networkinterfaceswatcher
Add DiscardKnownHosts option to utils/ssh
Allow restore to retry connecting to state server
Merge pull request #197 from axw/azure-network-affinitygroup

provider/azure: use affinity group in vnet site

Revert change based on observations of vnet
related issues. Azure console displays advisory
warning about vnets tied to locations, suggesting
vnets be tied to affinity groups to mitigate.