You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by "Chris A. Mattmann (Updated) (JIRA)" <ji...@apache.org> on 2012/04/01 00:30:35 UTC
[jira] [Updated] (OODT-275) Separate Resource Manager serialization
layers from interface implementations, like Monitor and JobQueue, out into
an upper layer wrapper
[ https://issues.apache.org/jira/browse/OODT-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann updated OODT-275:
-----------------------------------
Fix Version/s: (was: 0.4)
0.5
- push to 0.5
> Separate Resource Manager serialization layers from interface implementations, like Monitor and JobQueue, out into an upper layer wrapper
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: OODT-275
> URL: https://issues.apache.org/jira/browse/OODT-275
> Project: OODT
> Issue Type: Improvement
> Components: resource manager
> Environment: from JPL internal JIRA
> Reporter: Brian Foster
> Fix For: 0.5
>
>
> job, node, etc... serialization should be controlled by Resource Manager itself, however, the underlying serialization techniques used should still be customizable (i.e. introduction of a serialization interface for each set of information desired to be serialized - similar to JobRepository)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira