[jira] [Resolved] (OODT-764) Create a Resource Manager Backend That Muliplexes

["Michael Starch (JIRA)" <ji...@apache.org>]

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

Michael Starch resolved OODT-764.
---------------------------------
    Resolution: Fixed

Did the work, checked it in.

> Create a Resource Manager Backend That Muliplexes
> -------------------------------------------------
>
>                 Key: OODT-764
>                 URL: https://issues.apache.org/jira/browse/OODT-764
>             Project: OODT
>          Issue Type: New Feature
>          Components: resource manager
>            Reporter: Michael Starch
>            Priority: Minor
>             Fix For: 0.8
>
>
> If a user wants to run various jobs using different technologies behind the resource manager, then there needs to be a technology to choose between them.
> For example (scheduler is the key component of the resource manager backend):
> "mesos job" -> Mesos scheduler et. al.
> "spark job ->  Spark scheduler et. al.
> "normal job" -> Standard resource manager scheduler et. al.
> "torque job" -> Torque scheduler et. al.
> The natural place to make the switch is based on the queue that that job is in.  Thus we can create a resource manager backend that multiplexes jobs based on the queue that they are in.
> This can be accomplished by using XML configuration to map queues to backend sets, and create a custom set to multiplex between what is specified in XML.  The set must include the following:
> Muxing components:
>    -Scheduler
>    -Batchmgr
>    -Monitor
> Supporting components:
>    -Backend Manager - keeps track of children (Scheduler, Monitor, Batchmgr) and which queue these sets are associated.
>    -Backend repository - to setup BackendManager via config



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