Can you ask this question on the marathon mailing list?
On Fri, Jan 8, 2016 at 6:51 AM, Marica Antonacci <
[email protected]> wrote:
> Dear all,
>
> testing Marathon application/group deployment I have observed that if I
> try to deploy an application specifying a service port that has already
> been assigned to another app Marathon v2/apps endpoint rejects the request,
> as expected:
>
> {"message”:"Requested service port 8306 conflicts with a service port in
> app /dbaas01/mysql"}
>
> Yet, it seems that the service port uniqueness is not checked when
> submitting the deployment of an application group. I was able to deploy
> twice the same application group (changing the root group name) and using
> the same service ports for the applications.
> Of course, this creates an issue with the haproxy-marathon-bridge: the
> load balancer configuration is modified so that the same port points to
> different services:
>
> listen dbaas01_mysql-8306
> bind 0.0.0.0:8306
> mode tcp
> option tcplog
> balance leastconn
> server dbaas01_mysql-1 172.30.15.84:31841 check
>
> listen dbaas02_mysql-8306
> bind 0.0.0.0:8306
> mode tcp
> option tcplog
> balance leastconn
> server dbaas02_mysql-1 172.30.15.85:31075 check
>
> Is this the expected behavior? Why the check on the service port
> uniqueness is not performed on the application deployed using the
> /v2/groups endpoint?
>
> Thank you in advance for feedbacks.
> Best regards,
>
> Marica
>
>
> ----------------------------------------------------------
>
> Marica ANTONACCI
> INFN - National Institute of Nuclear Physics
> Via Orabona 4
> 70126 Bari - ITALY
> Phone +39 080 5443244
> Skype: marica.antonacci
> e-mail [email protected]
>
>
>
>
>
>
>
>
>
>
>
