aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam B (JIRA)" <>
Subject [jira] [Commented] (AURORA-1503) Determine how best to keep up with Mesos releases
Date Fri, 02 Oct 2015 21:10:27 GMT


Adam B commented on AURORA-1503:

In general, Mesos has aimed for +1/-1 version compatibility, so that a 0.22 libmesos should
be able to speak to a 0.23 master without issue, and a 0.23 master should be able to speak
to a 0.24 agent (although sometimes we ask that you upgrade masters before agents). See the
Mesos upgrade guide for upgrade procedures and important API changes and upgrade notes.

We provide more detail about each release, including JIRAs for breaking API changes in our

Since we've started a monthly release cadence, we are now discussing a time-based deprecation
cycle, rather than release-based.

> Determine how best to keep up with Mesos releases
> -------------------------------------------------
>                 Key: AURORA-1503
>                 URL:
>             Project: Aurora
>          Issue Type: Task
>            Reporter: Zameer Manji
>            Assignee: Zameer Manji
> Aurora 0.9.0 was released with a dependency on Mesos 0.22. The current release is Mesos
0.24. There was a change with how data was published into the Mesos ZK node in Mesos 0.23
(Protobuf to JSON) meaning that frameworks that are linked against 0.22 will get a libmesos
error when using the 0.24 library.
> The task is to determine what is the best way forward in scenarios like this. Possible
options include:
> * Release 0.9.x with a newer mesos dependency
> * Cut a new release from master that depends on 0.24
> Problems include backwards/forwards compatibility. For example if we release 0.9.1 with
a dependency on Mesos 0.24 will Aurora still work against a Mesos Master that runs 0.22?

This message was sent by Atlassian JIRA

View raw message