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 (JIRA)" <ji...@apache.org> on 2013/03/31 03:33:15 UTC

[jira] [Commented] (OODT-219) Monitor that plugs into Ganglia

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

Chris A. Mattmann commented on OODT-219:
----------------------------------------

Thanks Rajith, the former architecture diagram makes me confident that you can proceed. 
Of course, hooking into OODT will be a little different. I would take a look here first:

http://oodt.apache.org/components/maven/resource/user/
                
> Monitor that plugs into Ganglia
> -------------------------------
>
>                 Key: OODT-219
>                 URL: https://issues.apache.org/jira/browse/OODT-219
>             Project: OODT
>          Issue Type: New Feature
>          Components: resource manager
>         Environment: From JPL's internal JIRA.
>            Reporter: Chris A. Mattmann
>            Assignee: Chris A. Mattmann
>              Labels: gsoc2013
>             Fix For: 0.6
>
>         Attachments: image.png
>
>
> This project will contribute a ResourceMonitor plugin that reads information from Ganglia http://ganglia.info.
> The Apache OODT resource manager provides an AssignmentMonitor interface:
> http://oodt.apache.org/components/maven/apidocs/org/apache/oodt/cas/resource/monitor/AssignmentMonitor.html
> This allows plugging in of different tools externally or internal APIs and tools to monitor Jobs that are sent to ResourceNodes. 
> # Write a GangliaAssignmentMonitor and GangliaAssignmentMonitorFactory that plug in to Ganglia to obtain Job status information, and that construct GangliaAssignmentMonitors from a factory.
> # Write unit tests
> # Parse the Ganglia XML file to get the information from Ganglia

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira