[
https://issues.apache.org/jira/browse/OODT-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann updated OODT-11:
----------------------------------
Description:
Examples: Monitor and JobQueue. Make them an upper layer wrapper.
- 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)
was:
- 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)
Summary: Separate CAS-Resource serialization layers from interface
implementations (was: Separate CAS-Resource serialization layers from
interface implementations, like Monitor and JobQueue, out into an upper layer
wrapper)
- cleanup
> Separate CAS-Resource serialization layers from interface implementations
> -------------------------------------------------------------------------
>
> Key: OODT-11
> URL: https://issues.apache.org/jira/browse/OODT-11
> Project: OODT
> Issue Type: Improvement
> Components: resource manager
> Affects Versions: 0.1-incubating
> Environment: none
> Reporter: Brian Foster
> Priority: Minor
> Fix For: 0.2
>
>
> Examples: Monitor and JobQueue. Make them an upper layer wrapper.
> - 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.
-
You can reply to this email to add a comment to the issue online.
