aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Erb (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-828) Documentation could make a better job at selling aurora
Date Fri, 17 Oct 2014 17:44:33 GMT

    [ https://issues.apache.org/jira/browse/AURORA-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14175289#comment-14175289
] 

Stephan Erb commented on AURORA-828:
------------------------------------

Looks great, thanks!

> Documentation could make a better job at selling aurora
> -------------------------------------------------------
>
>                 Key: AURORA-828
>                 URL: https://issues.apache.org/jira/browse/AURORA-828
>             Project: Aurora
>          Issue Type: Story
>          Components: Documentation
>            Reporter: Stephan Erb
>            Assignee: Bill Farner
>              Labels: aurora-docday
>
> As a newcomer to Aurora, I would like the documentation to be more upfront with what
Aurora has to offer. 
> Some important questions:
> * What is the mission statement / elevator pitch of Aurora?
> * What features does it offer?  Are there any unique selling points I should know about?
(quota for production tasks, preemption of non-production tasks, zookeeper-based service discovery,
...)
> * Are there usecases it is NOT suited for?
> * Who is using it?
> We can learn from Marathon [[1|https://github.com/mesosphere/marathon]] [[2|https://mesosphere.github.io/marathon]]
and Singularity [[3|https://github.com/HubSpot/Singularity]] which are performing an excellent
job at selling their solution to a potential user.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message