[
https://issues.apache.org/jira/browse/MESOS-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Mathiske updated MESOS-2085:
----------------------------------
Sprint: Mesosphere Q4 Sprint 3 - 12/7, Mesosphere Q1 Sprint 1 - 1/23,
Mesosphere Q1 Sprint 2 - 2/6, Mesosphere Q1 Sprint 3 - 2/20, Mesosphere Q1
Sprint 4 - 3/6, Mesosphere Q1 Sprint 5 - 3/20, Mesosphere Q1 Sprint 6 - 4/3,
Mesosphere Q1 Sprint 7 - 4/17, Mesosphere Q2 Sprint 8 - 5/1, Mesosphere Q1
Sprint 9 - 5/15 (was: Mesosphere Q4 Sprint 3 - 12/7, Mesosphere Q1 Sprint 1 -
1/23, Mesosphere Q1 Sprint 2 - 2/6, Mesosphere Q1 Sprint 3 - 2/20, Mesosphere
Q1 Sprint 4 - 3/6, Mesosphere Q1 Sprint 5 - 3/20, Mesosphere Q1 Sprint 6 - 4/3,
Mesosphere Q1 Sprint 7 - 4/17, Mesosphere Q2 Sprint 8 - 5/1)
> Add support encrypted and non-encrypted communication in parallel for cluster
> upgrade
> -------------------------------------------------------------------------------------
>
> Key: MESOS-2085
> URL: https://issues.apache.org/jira/browse/MESOS-2085
> Project: Mesos
> Issue Type: Task
> Reporter: Niklas Quarfot Nielsen
> Assignee: Joris Van Remoortere
>
> During cluster upgrade from non-encrypted to encrypted communication, we need
> to support an interim where:
> 1) A master can have connections to both encrypted and non-encrypted slaves
> 2) A slave that supports encrypted communication connects to a master that
> has not yet been upgraded.
> 3) Frameworks are encrypted but the master has not been upgraded yet.
> 4) Master has been upgraded but frameworks haven't.
> 5) A slave process has upgraded but running executor processes haven't.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
