You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Benjamin Mahler (JIRA)" <ji...@apache.org> on 2017/03/29 22:21:41 UTC
[jira] [Commented] (MESOS-6762) Update release notes for multi-role
changes
[ https://issues.apache.org/jira/browse/MESOS-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15947997#comment-15947997 ]
Benjamin Mahler commented on MESOS-6762:
----------------------------------------
CHANGELOG update:
{noformat}
commit 10d7988ee5948bc45518e7c1c339a371c4bf151f
Author: Benjamin Mahler <bm...@apache.org>
Date: Thu Mar 16 15:33:56 2017 -0700
Added multi-role framework support to the CHANGELOG.
Review: https://reviews.apache.org/r/57707
{noformat}
Will close once the additional documentation described in this ticket is added.
> Update release notes for multi-role changes
> -------------------------------------------
>
> Key: MESOS-6762
> URL: https://issues.apache.org/jira/browse/MESOS-6762
> Project: Mesos
> Issue Type: Task
> Reporter: Benjamin Bannier
>
> When adding support for multi-role frameworks we should call out a number of potential issues in the changelog/release notes.
> This ticket collects potential pitfalls.
> h6. Changes in master and agent endpoints
> When rendering the {{FrameworkInfo}} of multi-role enabled frameworks in master or agent endpoints the {{role}} field will not be supported anymore; instead the {{roles}} field should be used. Any tooling parsing endpoint information and relying on the {{role}} field needs to be updated before multi-role enabled frameworks can be run in the cluster.
> h6. Changes to the allocator interface / implementation requirements for module implementors
> Implementors of allocator modules have to provide new implementation functionality to satisfy the MULTI_ROLE framework capability. Also, the interface has changed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)