[
https://issues.apache.org/jira/browse/AURORA-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14371411#comment-14371411
]
Bill Farner commented on AURORA-1212:
-------------------------------------
I'm afraid this raises bigger questions than it answers. How do you deal with
port conflicts? If these types of tasks are not dedicated, how do the clients
discover the host(s) they are on?
{quote}
In my environment I'd like to have static ports for some jobs to integrate with
some services that don't do service discovery, but I don't want to have to
partition my users up onto dedicated machines just for this.
{quote}
Crossing the service discovery bridge is indeed a challenge. Have you
considered alternative approaches like those mentioned in AURORA-761, or
[mesos-dns|https://github.com/mesosphere/mesos-dns]?
> Allow non-dedicated jobs to have static ports
> ---------------------------------------------
>
> Key: AURORA-1212
> URL: https://issues.apache.org/jira/browse/AURORA-1212
> Project: Aurora
> Issue Type: Story
> Reporter: Brian Brazil
>
> In my environment I'd like to have static ports for some jobs to integrate
> with some services that don't do service discovery, but I don't want to have
> to partition my users up onto dedicated machines just for this.
> Currently the aurora client rejects such a configuration, it should be
> allowed.
> https://github.com/apache/incubator-aurora/commit/bcabfce60d568d5d98c72109ee4493bce773a426
> was where this restriction was added.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
