You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@aurora.apache.org by "Bill Farner (JIRA)" <ji...@apache.org> on 2015/07/21 03:09:04 UTC

[jira] [Updated] (AURORA-1402) Allow overriding cluster attributes via environment variables

     [ https://issues.apache.org/jira/browse/AURORA-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bill Farner updated AURORA-1402:
--------------------------------
    Flagged: Impediment

> Allow overriding cluster attributes via environment variables
> -------------------------------------------------------------
>
>                 Key: AURORA-1402
>                 URL: https://issues.apache.org/jira/browse/AURORA-1402
>             Project: Aurora
>          Issue Type: Story
>            Reporter: Joe Smith
>            Assignee: Joe Smith
>
> An example usecase is giving the Aurora Client a different 'scheduler URI' which would allow the client to bypass a downed proxy but still be able to send RPCs. Initially it seemed like this would be the only usecase, but after speaking to [~wfarner] and [~kevints], a more general solution to override various parts of a cluster configuration would be useful.
> There is already a [mechanism to go from a cluster's json|https://github.com/apache/aurora/blob/master/src/main/python/apache/aurora/admin/admin.py#L494], so we should consider using the same formatting to make that read+write, vs. just read.



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