Override the kubernetes or docker native ReST port number

Registered by Steven Dake on 2015-01-08

Users of Magnum may want to use different ports per bay. Suggest adding a property to the baymodel object to indicate the ReST endpoint atleast for kubernetes. I don't think we will be able to override the port of docker unfortunately (I suspect technically not possible). Initially lets just try to tackle overriding the ReST API port via the heat template.

Blueprint information

Adrian Otto
Steven Dake
Needs approval
Guangya Liu (Jay Lau)
Series goal:
Good progress
Milestone target:
Started by
Steven Dake
Completed by
Adrian Otto

Related branches



Gerrit topic: https://review.openstack.org/#q,topic:bp/override-native-rest-port,n,z

Addressed by: https://review.openstack.org/146275
    Add apiserver_port to BayModel

Addressed by: https://review.openstack.org/146859
    Remove k8s_port from kube.py

adrian_otto: What work is remaining for implementation of this feature? Should this be marked as Implemented?

We need to update template to support customizing api server port. --jay-lau-513 2015-01-28513 2015-01-28

After some discussion with larsks, it seems that it does not make much sense to customize this port as the k8s cluster will be created by heat and end user do not need to care the ports, so I suggest that we can defer this or take this as low priority, comments? -jay-lau-513 2015-01-30

I think this use case came about by me thinking the port would be shared between all of the infrastructure. Instead, because of the way bay's work, Neutron will isolate the network. So I agree, I think we can probably just drop this blueprint unless someone comes up with a good use case for it. Sorry for the wasted effort :( We need better validation of the blueprints to make sure they make sense before we begin implementation in the future --sdake


Work Items

This blueprint contains Public information 
Everyone can see this information.