You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Guangya Liu (JIRA)" <ji...@apache.org> on 2015/11/06 11:33:27 UTC
[jira] [Updated] (MESOS-3838) Put authorize logic for teardown into
a common function
[ https://issues.apache.org/jira/browse/MESOS-3838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guangya Liu updated MESOS-3838:
-------------------------------
Description:
The mesos now have {{authorizeTask}}, {{authorizeFramework}} and may have {{authorizeReserveResource}} and {{authorizeUnReserveResource}} later.
But now the {{Master::Http::teardown()}} is putting the authorize logic in the {{Master::Http::teardown()}} itself, it is better to put authorize logic for teardown into a common function {{authorizeTeardown()}}.
was:
The mesos now have authorizeTask, authorizeFramework and may have authorizeReserveResource and authorizeUnReserveResource later.
But now the Master::Http::teardown() is putting the authorize logic in the Master::Http::teardown() itself, it is better to put authorize logic for teardown into a common function authorizeTeardown().
> Put authorize logic for teardown into a common function
> -------------------------------------------------------
>
> Key: MESOS-3838
> URL: https://issues.apache.org/jira/browse/MESOS-3838
> Project: Mesos
> Issue Type: Bug
> Reporter: Guangya Liu
> Assignee: Guangya Liu
>
> The mesos now have {{authorizeTask}}, {{authorizeFramework}} and may have {{authorizeReserveResource}} and {{authorizeUnReserveResource}} later.
> But now the {{Master::Http::teardown()}} is putting the authorize logic in the {{Master::Http::teardown()}} itself, it is better to put authorize logic for teardown into a common function {{authorizeTeardown()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)