[
https://issues.apache.org/jira/browse/AURORA-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill Farner resolved AURORA-219.
--------------------------------
Resolution: Won't Fix
Closing, as i think the ticket is underspecified and not actionable. I'm also
not sure this should be done — frameworks should be free to choose their own
communication mechanisms and formats. Without a common protocol, data format,
or schema, i don't see a tractable way forward on this.
> Aurora/Mesos Client Generalization
> ----------------------------------
>
> Key: AURORA-219
> URL: https://issues.apache.org/jira/browse/AURORA-219
> Project: Aurora
> Issue Type: Story
> Components: Client
> Reporter: Dave Lester
> Labels: gsoc2014
>
> Aurora provides an interface to scheduling, running, and monitoring commands
> on a Mesos cluster. Other frameworks besides Aurora provide similar
> capabilities for some key functions. A general command client could abstract
> details of specific frameworks, and provide these functions for all
> frameworks.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
