Opened 14 years ago

Last modified 11 years ago

#864 new task

IZ148: document the current decission making process

Reported by: easymf Owned by:
Priority: normal Milestone:
Component: hedeby Version: 1.0
Severity: minor Keywords: doc


[Imported from gridengine issuezilla]

        Issue #:      148          Platform:     All         Reporter: easymf (easymf)
       Component:     hedeby          OS:        All
     Subcomponent:    doc          Version:      1.0            CC:    None defined
        Status:       NEW          Priority:     P1
      Resolution:                 Issue type:    TASK
                               Target milestone: 1.0u5next
      Assigned to:    easymf (easymf)
      QA Contact:     adoerr
       * Summary:     document the current decission making process
   Status whiteboard:

     Issue 148 blocks:
   Votes for issue 148:     Vote for this issue

   Opened: Thu Oct 11 02:40:00 -0700 2007 

   Specification has to be updated to contain a clear description of the decision
   making process.
               ------- Additional comments from easymf Thu Oct 18 08:54:08 -0700 2007 -------
   work has been started
               ------- Additional comments from easymf Tue Aug 5 05:40:10 -0700 2008 -------
   it should be a description of algorithm and thus should be done not in spec, but
   in JDoc, ideally in ResourceManagerImpl.
               ------- Additional comments from easymf Wed Aug 6 04:07:08 -0700 2008 -------

   Decision process algorithm is not clearly documented - there is no description
   of request workflow that causes resource to be assigned to a service as a result
   of service's request.


   To avoid bugs in implementation and allow further enhancements, we need to fix this.

   Suggested Fix/Work Around

   No workaround, just to fix it - provide a description of algorithm in resource
   manager class.



   How to test


   ATC: 0.1 PD
   ETC: 1 PD
               ------- Additional comments from adoerr Wed Aug 6 05:26:26 -0700 2008 -------
   According to the Issue Tracker entry format rules, the analysis section of a
   documentation task should list the exact chapters and sections of the
   documentation that should be updated / added. Please add this information.

               ------- Additional comments from easymf Wed Aug 6 05:37:11 -0700 2008 -------
   Updated analysis:

   Documentation chapter/section affected: none/none (spec should not contain
   algorithm descriptions, just high-level stuff).

   Affected JDoc (for class)             : ResourceManagerImpl$ResourceRemovedAction

               ------- Additional comments from rhierlmeier Wed Nov 25 07:21:12 -0700 2009 -------
   Milestone changed

Change History (1)

comment:1 Changed 11 years ago by dlove

  • Priority changed from highest to normal
  • Severity set to minor
Note: See TracTickets for help on using tickets.