WIP: Add election framework to master; publish services.

Needs tests still.
Yeah, I'm not totally opposed to these being in a master object that does with a lock, I just don't know that the blanket master / slave distinction is appropriate yet.  For instance, pods and repl controller writes don't need to go through the master.


> On Oct 21, 2014, at 11:27 AM, Eric Tune <notifications@github.com> wrote:
> 
> In pkg/master/publish.go:
> 
> > +WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> > +See the License for the specific language governing permissions and
> > +limitations under the License.
> > +*/
> > +
> > +package master
> > +
> > +import (
> > +	"time"
> > +
> > +	"github.com/GoogleCloudPlatform/kubernetes/pkg/api"
> > +
> > +	"github.com/golang/glog"
> > +)
> > +
> > +func (m *Master) serviceWriterLoop(stop chan struct{}) {
> To the ip address allocation: I guess your answer would be that the next-ip-address goes in etcd and is accessed using some kind of lock.
> …
> —
> Reply to this email directly or view it on GitHub.