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] [Resolved] (AURORA-181) make TaskObserver deal in objects
Date Mon, 28 Dec 2015 02:48:49 GMT

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

Bill Farner resolved AURORA-181.
--------------------------------
    Resolution: Won't Fix

>  make TaskObserver deal in objects 
> -----------------------------------
>
>                 Key: AURORA-181
>                 URL: https://issues.apache.org/jira/browse/AURORA-181
>             Project: Aurora
>          Issue Type: Task
>          Components: Thermos
>            Reporter: Jonathan Boulle
>            Priority: Minor
>
> Per the long-lived comment on the TaskObserver class in apache/thermos/observer/observer.py
; now that there are new first-class objects for representing observed tasks (ActiveObservedTask,
FinishedObservedTask), the TaskObserver should just return them for all queries, instead of
generating janky dictionaries (which the HTTP observer often ends up doing further mangling
of anyway).
> This would
> a) lead to a much cleaner interface between the TaskObserver and the BottleObserver (currently
the only real interface to the observer)
> b) make the TaskObserver much more usable as an API or even for command line use
> c) make it much easier to develop other interfaces to the observer, e.g. a pure JSON-over-HTTP
service



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

Mime
View raw message