aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Farner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-790) Resources field should belong to aurora, not thermos
Date Fri, 03 Oct 2014 00:52:33 GMT

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

Bill Farner commented on AURORA-790:
------------------------------------

Just to add context, i assume you mean this?
https://github.com/apache/incubator-aurora/blob/467f84285d7fd0c9f861b839f25449b194e391e4/src/main/python/apache/thermos/config/schema_base.py#L38-L41

> Resources field should belong to aurora, not thermos
> ----------------------------------------------------
>
>                 Key: AURORA-790
>                 URL: https://issues.apache.org/jira/browse/AURORA-790
>             Project: Aurora
>          Issue Type: Task
>          Components: Client, Executor, Thermos
>            Reporter: brian wickman
>
> Thermos doesn't care about Resources, yet it owns the specification of them.  We should
move the Resource definition schema to the Job struct from the Task struct.



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

Mime
View raw message