aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Farner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-1569) Support custom serverset path for announcements
Date Wed, 30 Dec 2015 23:31:49 GMT

    [ https://issues.apache.org/jira/browse/AURORA-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15075513#comment-15075513
] 

Bill Farner commented on AURORA-1569:
-------------------------------------

I'm afraid this might create more issues than it solves.  In addition to security/cross-talk
issues (services registering as each other, whether accidental or nefarious), there is valuable
naming consistency lost by making this free-form.  If you can keep your service registry from
becoming the wild west (and furthermore - restrict writes to the service registration path
with ACLS), it will really pay off in the long run.

[~coder_kk] is the flexibility you're after because you would like a different format, or
are there other factors at play?

> Support custom serverset path for announcements
> -----------------------------------------------
>
>                 Key: AURORA-1569
>                 URL: https://issues.apache.org/jira/browse/AURORA-1569
>             Project: Aurora
>          Issue Type: Story
>          Components: Executor
>            Reporter: Kunal Thakar
>
> The Announcer serverset path is not flexible enough. You can only change the root of
the path (/$ROOT/role/environment/jobname). As a user with different service discovery schema,
this doesn't fit our needs. We want to be able to specify the serverset announce path with
the job spec.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message