[
https://issues.apache.org/jira/browse/MESOS-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Mahler updated MESOS-338:
----------------------------------
Description:
This is to establish a roadmap for the desired features for 1.0.0, this is not
meant to be an authoritative list!
Slave Recovery: MESOS-110
Master State Registrar: MESOS-295
New API: (no ticket yet)
Using Futures to replace callbacks and as a means of acknowledgement.
First Class "grandfathered" Resources (e.g. cpu, memory, disk, ...).
Security and Authentication: MESOS-418
Reconfigurable Log: MESOS-683
Stateful Scheduler Driver: (no ticket yet)
Revocable offers: (no ticket yet)
Packaging: (needs an umbrella ticket)
Launching Frameworks: (no ticket yet)
was:
This is to establish a list of pre-1.0.0 release breaking changes we'd like to
get in:
Definitely:
-Slave Recovery: MESOS-110
-Resource Monitoring: MESOS-324
Others:
-Executor Restart
-Using protobuf -> JSON conversion: MESOS-269
Maybe not _breaking_:
-Adding timestamps to Tasks / Status Updates.
-Making Resources First-Class (i.e. cpus, mem, disk, network, etc).
-Adding cpu Resource types, e.g. {SOFT, HARD, PINNED}
> 1.0.0 Roadmap
> -------------
>
> Key: MESOS-338
> URL: https://issues.apache.org/jira/browse/MESOS-338
> Project: Mesos
> Issue Type: Story
> Reporter: Benjamin Mahler
> Priority: Critical
>
> This is to establish a roadmap for the desired features for 1.0.0, this is
> not meant to be an authoritative list!
> Slave Recovery: MESOS-110
> Master State Registrar: MESOS-295
> New API: (no ticket yet)
> Using Futures to replace callbacks and as a means of acknowledgement.
> First Class "grandfathered" Resources (e.g. cpu, memory, disk, ...).
> Security and Authentication: MESOS-418
> Reconfigurable Log: MESOS-683
> Stateful Scheduler Driver: (no ticket yet)
> Revocable offers: (no ticket yet)
> Packaging: (needs an umbrella ticket)
> Launching Frameworks: (no ticket yet)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
