services stop and start as hosts are added and removed

fixes zen-13093
I'm not saying to exit the loop if the node goes away; it can wait if the
node goes away.  It should exit the loop when the channel is closed, the
channel is only closed if the agent, in your example the master/agent, is
shutdown.

Ultimately there is no clear exit out of the loop when the shutdown channel
is closed, there should be a clear exit/return when the shutdown channel is
closed


On Tue, Jul 29, 2014 at 2:09 PM, smousa <notifications@github.com> wrote:

> In node/agent.go:
>
> >
> > -	wg.Add(1)
> > -	go func() {
> > -		defer wg.Done()
> >  		zzk.Start(shutdown, hsListener, virtualIPListener, actionListener)
>
> However,
> Say you have a master that is also running as an agent. You delete that
> host from the pool and then later you add it back again. That means you
> have to bounce the master in order for that host to start managing
> containers. Is that acceptable
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/control-center/serviced/pull/790/files#r15545159>.
>