Enhancement/29 port resources

[philwinder]

Working port injection. …

• Refactor docker configuration options into DockerConfigProperties
• Add new PortRequirement
• Add port parser to parse different types of ports (fixed, unprivileged, privileged)
• No longer publish all ports (will be published in Host mode)
• Add properties to expose ports through env vars
• Host/Bridge mode.

Working host example:

spring.application.name=kibana
mesos.framework.name=kibana
mesos.resources.scale=3
mesos.resources.cpus=0.5
mesos.resources.mem=256
mesos.command=kibana --port=$UI_5061 --elasticsearch http://172.17.0.2:9200
mesos.resources.ports=true
mesos.resources.ports.UI_5061=ANY
mesos.docker.network=HOST
mesos.docker.image=kibana:latest

Working bridge example:

spring.application.name=kibana
mesos.framework.name=kibana
mesos.resources.scale=3
mesos.resources.cpus=0.5
mesos.resources.mem=256
mesos.command=kibana --port=$UI_5061 --elasticsearch http://172.17.0.2:9200
mesos.resources.ports=true
mesos.resources.ports.UI_5061=ANY
mesos.docker.parameter.expose=$UI_5061
mesos.docker.network=BRIDGE
mesos.docker.image=kibana:latest

Working jar mode:

spring.application.name=kibana
mesos.framework.name=kibana
mesos.resources.scale=3
mesos.resources.cpus=0.5
mesos.resources.mem=256
mesos.command=curl -sS -q -o kibana.tar.gz https://download.elastic.co/kibana/kibana/kibana-4.4.1-linux-x64.tar.gz > /dev/null ; tar -zxf kibana.tar.gz ; cd kibana-* ; bin/kibana --port=$UI_5061 --elasticsearch http://172.17.0.2:9200
mesos.resources.ports=true
mesos.resources.ports.UI_5061=ANY

Fixes #27 and #29

[mwl]

@philwinder Looks like there's a merge conflict with Master

[philwinder]

There is a problem with this line: https://github.com/ContainerSolutions/mesos-starter/blob/master/spring-boot-starter-mesos/src/main/java/com/containersolutions/mesos/config/autoconfigure/MesosSchedulerConfiguration.java#L169

A map isn't considered to be a present property. So when a user applies a port requirement, the port requirement isn't instantiated.

[mwl]

Didn't you rename it to plural ports?

[mwl]

Working bridge example:

spring.application.name=kibana mesos.framework.name=kibana mesos.resources.scale=3 mesos.resources.cpus=0.5 mesos.resources.mem=256 mesos.command=kibana --port=$UI_5061 --elasticsearch http://172.17.0.2:9200 mesos.resources.ports=true mesos.resources.ports.UI_5061=ANY mesos.docker.parameter.expose=$UI_5061 mesos.docker.network=BRIDGE mesos.docker.image=kibana:latest

Documentation seems wrong? Value of $UI_5061 is the port from the Mesos Resources (i.e. 31000). To me it makes no sense to start Kibana on that port, and expose it when in Bridge mode. Normally you never touch the container ports when in Bridge mode. You just map them to $UI_5061 on the host.

[mwl]

Solved in #39