[
https://issues.apache.org/jira/browse/MESOS-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326585#comment-14326585
]
Vinod Kone commented on MESOS-2372:
-----------------------------------
We had an internal testing framework (written in python and built on top of
pytest) that sort of filled this gap. It was mainly aimed at doing fault
tolerant testing (process faults, zk faults) on aurora + mesos cluster spun on
a single host. It also had support for running different versions of masters,
slaves and frameworks. I'll be happy to share that code as a starting point.
Having said that, I'm looking for something very simple here. A Jenkins job
that builds 2 different versions (v1: current HEAD and v2: last released
version) of mesos and bring up single master (v1 or v2) and slave (v1 or v2)
and run the long lived framework or mesos-execute (v1 or v2 libs).
> Test suite for verifying compatibility between Mesos components
> ---------------------------------------------------------------
>
> Key: MESOS-2372
> URL: https://issues.apache.org/jira/browse/MESOS-2372
> Project: Mesos
> Issue Type: Epic
> Reporter: Vinod Kone
> Assignee: Niklas Quarfot Nielsen
>
> 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)
