Using hostname instead of ocho-proxy to enable with replication controll...

autodesk-cloud / ochopod

Your friendly orchestration overlay over Mesos, K8S and more !

http://autodesk-cloud.github.io/ochopod/

Apache License 2.0

122 stars 20 forks source link

Using hostname instead of ocho-proxy to enable with replication controll... #5

Closed stphung closed 9 years ago

stphung commented 9 years ago

Using env['HOSTNAME'] instead of ocho-proxy to look up pod information, this allows the pod to succeed in pod information lookup no matter what the name of the pod is. (Replication controller support)

opaugam commented 9 years ago

Beep .. you can't do that. Keep in mind the bindings are run by any ocho container out there. If you lookup on $HOSTNAME you'll look yourself up. This will work right now for the portal (since ZK is co-located on that pod) but fail for everybody else..

stphung commented 9 years ago

Whoops, yes that makes sense, need to essentially do the following for this to work:

First create portal replication controller with a well defined name, say "portal-replication-controller".
Bindings look up the replication controller by name "portal-replication-controller".
Look for the pod inside the portal replication controller and use that as the ip.

I'll close this pull request and open another later, thanks for the catch and feedback.