Opened 14 years ago

Last modified 10 years ago

#1080 new enhancement

IZ139: Testsuite should support additional cell clusters using the same hosts

Reported by: crei Owned by:
Priority: normal Milestone:
Component: testsuite Version: current
Severity: Keywords: Sun framework


[Imported from gridengine issuezilla]

        Issue #:      139             Platform:     Sun           Reporter: crei (crei)
       Component:     testsuite          OS:        All
     Subcomponent:    framework       Version:      current          CC:    None defined
        Status:       NEW             Priority:     P3
      Resolution:                    Issue type:    ENHANCEMENT
                                  Target milestone: milestone 1
      Assigned to:    issues@testsuite
      QA Contact:     joga
       * Summary:     Testsuite should support additional cell clusters using the same hosts
   Status whiteboard:

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

   Opened: Tue Aug 7 05:36:00 -0700 2007 

Currently the testsuite doesn't support additional cell clusters
which are using the same hosts. Reason is that the shutdown procedures
(or some other ps specific code) always searching for processes which
have the SGE_ROOT path in the psinfo string.

On additional cell cluster hosts using the same hosts the testsuite cannot
distinguish between the processes and which process belongs to which cell.

Pos. Solution: When shutting down processes the pid file have to be used
to check whether the process really belongs to the actual cluster which
have to be shutdown.

The testsuite also have to be checked if the shutdown procedures are the
only reason for breaking additional cell support or if there are also other
tests which might have problems with the additional cell processes.

If the testsuite is able to support addtional cells on the same hosts the
additional testsuite config checks which currently report errors if the
same hosts are used for add. cell clusters can be removed.

See TODO: comment for this issue # in the tcl_files/config.tcl file

Change History (0)

Note: See TracTickets for help on using tickets.