Lack of port mapping functionality
Bug #1561514 reported by
Daniel
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla-mesos |
New
|
Undecided
|
Unassigned |
Bug Description
Hello,
I noticed that all services deployed via Marathon use a flag "net=host". IMHO if we have all information about ports required by application, kolla-mesos should deploy that service with option port mapping. Port mapping allow to use marathon-lb with those services. I think that you should replace net=host or give a functionality to choose between net=host and port mapping.
To post a comment you must log in.
If you don't want to change "net=host" because of possibilities of performance loss you can just add two new lines to application json.
"ports": [All ports required by service, comma separated],
"requirePorts": true
It allows to use Services via Marathon-lb.