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/02/03 21:44:34 UTC

[jira] [Commented] (AURORA-1091) Ability to put the scheduler into read-only mode

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

Bill Farner commented on AURORA-1091:
-------------------------------------

Generic authorization configuration could be one approach to leverage here.

> Ability to put the scheduler into read-only mode
> ------------------------------------------------
>
>                 Key: AURORA-1091
>                 URL: https://issues.apache.org/jira/browse/AURORA-1091
>             Project: Aurora
>          Issue Type: Story
>          Components: Reliability
>            Reporter: Joe Smith
>
> There may be situations where an external event may warrant putting the scheduler into a 'read-only' mode where it ignores external (aka, user-driven) input.
> Having a command line flag to toggle this would allow for read-only operations (such as the web UI) to continue serving traffic while preventing possibly dangerous changes to the cluster.



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