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

Alexander Rojas commented on MESOS-4840:
----------------------------------------

So as we saw, the {{TeardownFramework}} protobuf was only introduced in Mesos 
0.27.0 so it hasn't reached the end of deprecation period, however we should 
internally remove as much as possible the {{ShutdownFramework}}. The proposed 
behavior is then:

# When loading the ACLs if both {{teardown_frameworks}} and 
{{shutdown_frameworks}} are defined, we print a warning and use exclusively the 
teardown acls.
# If only {{shutdown_frameworks}} are defined, internally we copy its contents 
to the {{teardown_frameworks}} and use those exclusively.
# If only  {{teardown_frameworks}} we use those exclusively.

References to {{ShutdownFramework}} are to be kept only to the code that 
executes the steps mentioned previously. The message however needs to stay in 
the protocol for a while.



> Remove ShutdownFramework from the ACLs messages and references
> --------------------------------------------------------------
>
>                 Key: MESOS-4840
>                 URL: https://issues.apache.org/jira/browse/MESOS-4840
>             Project: Mesos
>          Issue Type: Task
>          Components: master, security, technical debt
>    Affects Versions: 0.28.0
>            Reporter: Alexander Rojas
>            Assignee: Alexander Rojas
>            Priority: Minor
>              Labels: deprecation, mesosphere
>
> {{ShutdownFramework}} acl was deprecated a couple of versions ago in favor of 
> the {{TeardownFramework}} message. Its deprecation cycle came with 0.27. That 
> means we should remove the message and its references in the code base.



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

Reply via email to