Comment 9 for bug 1529760

@Ton Ngo
How about this idea? Booting a new service called magnum-watcher.
magnum-watcher will make use of the "service watch" of kubernetes api. When any change of kubernetes service happens, magnum-watcher will catch it. Then the magnum-watcher starts a new task to list the services and create/delete/update load balancers for the service. Then, magnum-watcher watches k8s service again and waited for next change.
magnum-watcher is also defined in template and created by stack. when stack is deleted, magnum-watcher will clean all the LBs and some other infos.