IZ1539: configurable "out of order" comments queue/host

[jmarconnet]

[Imported from gridengine issuezilla ​http://gridengine.sunsource.net/issues/show_bug.cgi?id=1539]

        Issue #:      1539             Platform:     All      Reporter: jmarconnet (jmarconnet)
       Component:     gridengine          OS:        All
     Subcomponent:    gui              Version:      6.0u3       CC:    None defined
        Status:       NEW              Priority:     P4
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    andre (andre)
      QA Contact:     andre
          URL:
       * Summary:     configurable "out of order" comments queue/host
   Status whiteboard:
      Attachments:

     Issue 1539 blocks:
   Votes for issue 1539:  3


   Opened: Fri Apr 1 13:36:00 -0700 2005 
------------------------


It would be helpful for the day to day administrators to be able within qmon
to set and to review free text comments to ques and/or hosts such as: "Bob's
Dept. use only", "out for repair", "repaired 2/2/2002", "flakey", "empty
slot", "minimal RAM", "new RAM on order", etc.

Accordingly it would be desirable to be able to review these comments using
qstat and qhost.

A temporary workaround using the current software is to add a complex (string)
entry such as "comment", and then to attach comments as desired to queues
and/or hosts.

   ------- Additional comments from andreas Mon Apr 4 01:59:34 -0700 2005 -------
SUGGESTED FIX:
(1) qmod could be enhanced to allow out of order comments be configured for
    a queue or queue instances of a particular host
(2) qstat -explain would have to display those comments
(3) when queue becomes availabile again "out of order" comments would become
    invalid and thus would have to be automatically deleted by N1GE
as a matter of course (1) and (2) must be doable also via qmon

   ------- Additional comments from andreas Mon Apr 4 02:24:29 -0700 2005 -------
Addenum:
If complexes are used as workaround there might be a problem with out of order
comments that contain whitespaces. If necessary whitespaces need to be replaced
with underscores.