aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maxim Khutornenko (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AURORA-1503) Determine how best to keep up with Mesos releases
Date Mon, 12 Oct 2015 18:21:06 GMT

     [ https://issues.apache.org/jira/browse/AURORA-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Maxim Khutornenko updated AURORA-1503:
--------------------------------------
    Sprint: Twitter Aurora Q4'15 Sprint 13, Twitter Aurora Q4'15 Sprint 14  (was: Twitter
Aurora Q4'15 Sprint 13)

> Determine how best to keep up with Mesos releases
> -------------------------------------------------
>
>                 Key: AURORA-1503
>                 URL: https://issues.apache.org/jira/browse/AURORA-1503
>             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
(v6.3.4#6332)

Mime
View raw message