ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nate Cole (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-18680) Add orchestration for HOST_ORDERED upgrades
Date Tue, 25 Oct 2016 19:48:59 GMT

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

Nate Cole updated AMBARI-18680:
-------------------------------
    Summary: Add orchestration for HOST_ORDERED upgrades  (was: Disallow POST and PUT operations
on a cluster)

> Add orchestration for HOST_ORDERED upgrades
> -------------------------------------------
>
>                 Key: AMBARI-18680
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18680
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>            Reporter: Nate Cole
>            Assignee: Nate Cole
>            Priority: Critical
>             Fix For: 2.5.0
>
>
> When invoking an Offline Upgrade, the server should be restricted for operation by the
web client.
> * We can add a servlet filter to restrict this, then use a {{cluster-env}} property to
indicate when the API should be locked down. 
> * PUT/POST should all be disallowed
> ** Except when passing a custom header with calls that allows the functionality.



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

Mime
View raw message