You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Bernd Mathiske (JIRA)" <ji...@apache.org> on 2015/05/01 17:24:11 UTC
[jira] [Updated] (MESOS-2372) Test suite for verifying
compatibility between Mesos components
[ https://issues.apache.org/jira/browse/MESOS-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bernd Mathiske updated MESOS-2372:
----------------------------------
Sprint: 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 Q1 Sprint 5 - 3/20, Mesosphere Q1 Sprint 6 - 4/3, Mesosphere Q1 Sprint 7 - 4/17, Mesosphere Q2 Sprint 8 - 5/1)
> Test suite for verifying compatibility between Mesos components
> ---------------------------------------------------------------
>
> Key: MESOS-2372
> URL: https://issues.apache.org/jira/browse/MESOS-2372
> Project: Mesos
> Issue Type: Task
> Reporter: Vinod Kone
> Assignee: Kapil Arya
>
> While our current unit/integration test suite catches functional bugs, it doesn't catch compatibility bugs (e.g, MESOS-2371). This is really crucial to provide operators the ability to do seamless upgrades on live clusters.
> We should have a test suite / framework (ideally running on CI vetting each review on RB) that tests upgrade paths between master, slave, scheduler and executor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)