Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between pages "PTP/designs/rm view" and "CDT/Developer/FAQ"

< PTP‎ | designs(Difference between pages)
m (Interface: IRMResourceManagerListener)
 
m
 
Line 1: Line 1:
This is a preliminary design for the PTP Resource Management system. This is the design of the first phase product, which is limited in scope to viewing the state of the resource manager.  This includes the machines, jobs, queues, and nodes that are under the resource manager's control. The classes currently in PTP will implement these new interfaces in addition to their previously implemented interfaces.
+
== General ==
  
== Package resourcemanager ==
+
* Is it fun writing code for the CDT?
  
For interfaces and abstract classes, the responsibilities and collaborations refer to concrete objects that are implementations of the interface or abstract class.
+
You betcha! And the Eclipse SDK is such a great environment to work in. We've pumped out quality code by the boat load without a lot of effort.
  
=== Interface: IRMResourceManager ===
+
== Release Engineering ==
  
; Responsibilities:  Proxy used to connect to the ResourceManagerHost's actual resource manager (ARM).<br> Retrieve list of machines, nodes, jobs, process, and queues from ARM.<br>  Notify registered objects that the lists have changed, either in composition, or in their element's attributes due to changes propagated from the ARM
+
* Where can I get the latest builds?
; Collaborations:    IRMResourceManagerHost<br> IRMResourceManagerListener<br> IRMResourceManagerEvent<br> IRMMachine, IRMNode, IRMJob, IRMQueue
+
  
=== Interface: IRMResourceManagerListener ===
+
We have a build machine, [http://cdt.eclipse.org cdt.eclipse.org], that we use for our builds. You can access them from the builds section on its home page. You can also generate your own builds by checking out the CDT out of CVS and using the Export -> Deployable Feature menu item provided by the PDE.
 
+
; Responsibilities:  Registration site for Observer pattern to allow objects to be notified of changes in the IRMResourceManager's status
+
 
+
;Collaborations:    IRMResourceManager<br> IRMEvent
+
 
+
=== Interface: ResourceManagerEvent ===
+
 
+
  Responsibilities:  Determine type of changed in the
+
IRMResourceManager's
+
    state
+
 
+
  Collaborations:   
+
 
+
=== Class: ResourceManagerHost ===
+
 
+
  Responsibilities:  Determine which remote (or local) host's resource
+
      manager to proxy
+
      Determine which resource manager on the host to
+
      proxy
+
 
+
  Collaborations:
+
 
+
=== Interface: IRMMachine ===
+
 
+
  Responsibilities:  Provide the status information, i.e. attributes,
+
      for the ARM's associated machine
+
      Provide specific attributes for a given
+
      attribute description
+
      List all nodes associated with ARM's
+
      machine
+
 
+
  Collaborations:     IAttribute
+
      IAttrDesc
+
 
+
=== Interface: IRMQueue ===
+
 
+
  Responsibilities:  Provide the status information, i.e. attributes,
+
      for the ARM's associated queue
+
      Provide specific attributes for a given
+
      attribute description
+
      List all nodes that may have jobs dispatched
+
      from this queue
+
 
+
  Collaborations:    IAttribute
+
      IAttrDesc
+
 
+
=== Interface: IRMNode ===
+
 
+
  Responsibilities:  Provide the status information, i.e. attributes,
+
      for the ARM's associated node
+
      Provide specific attributes for a given
+
      attribute description
+
      List all jobs associated with ARM's
+
      node
+
      List all queues that can run jobs on this
+
      node
+
 
+
  Collaborations:    IAttribute
+
      IAttrDesc
+
 
+
=== Interface: IRMJob ===
+
 
+
  Responsibilities:  Provide the status information, i.e. attributes,
+
      for the ARM's associated job
+
      Provide specific attributes for a given
+
      attribute description
+
      List all processes associated with ARM's
+
      job
+
 
+
  Collaborations:    IAttribute
+
      IAttrDesc
+
 
+
=== Interface:  IRMProcess ===
+
 
+
  Responsibilities:  Provide the status information, i.e. attributes,
+
      for the ARM's associated process
+
      Provide specific attributes for a given
+
      attribute description
+
 
+
  Collaborations:    IAttribute
+
      IAttrDesc
+
 
+
=== Interface: IAttribute ===
+
 
+
  Responsibilities:  Maintain the relationship between an attribute's
+
value
+
      and its description
+
      Specifies a strict-weak ordering of itself and
+
      other attributes
+
      Provide a string representation of the attribute
+
 
+
  Collaborations:    IAttrDesc
+
 
+
=== Interface: IAttrDesc ===
+
 
+
  Responsibilities:  Provide a string description of the attribute
+
      Provide a name of the attribute
+
      Know the actual type of the attribute
+
      Create new attributes of the correct type
+
 
+
  Collaborations:    IAttribute
+

Revision as of 14:01, 5 May 2006

General

  • Is it fun writing code for the CDT?

You betcha! And the Eclipse SDK is such a great environment to work in. We've pumped out quality code by the boat load without a lot of effort.

Release Engineering

  • Where can I get the latest builds?

We have a build machine, cdt.eclipse.org, that we use for our builds. You can access them from the builds section on its home page. You can also generate your own builds by checking out the CDT out of CVS and using the Export -> Deployable Feature menu item provided by the PDE.

Back to the top