Opened 14 years ago

Last modified 10 years ago

#989 new enhancement

IZ48: Specify preferred exec host for test runs

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


[Imported from gridengine issuezilla]

        Issue #:      48              Platform:     All           Reporter: joga (joga)
       Component:     testsuite          OS:        All
     Subcomponent:    framework       Version:      current          CC:    None defined
        Status:       RESOLVED        Priority:     P3
      Resolution:     FIXED          Issue type:    ENHANCEMENT
                                  Target milestone: milestone 1
      Assigned to:    issues@testsuite
      QA Contact:     joga
       * Summary:     Specify preferred exec host for test runs
   Status whiteboard:

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

   Opened: Thu Nov 16 08:42:00 -0700 2006 

This was IZ 1312 in project gridengine.

To test a specific architecture, it should be
possible to specify which exec host shall be used
to perform the execd specific tests.

   ------- Additional comments from joga Fri Nov 17 01:39:57 -0700 2006 -------
Specifying a preferred architecture might also be an option, e.g. when we need
to test on multiple hosts of same architecture.

   ------- Additional comments from joga Fri Dec 22 00:51:23 -0700 2006 -------
Introduced a function "host_conf_get_best_exec_hosts",
that could be the place where to implement this rfe.

   ------- Additional comments from joga Wed Apr 4 23:33:35 -0700 2007 -------
Enhanced the function
to take
- a list of preferred architectures
- a list of selected architectures
- a list of excluded architectures

It returnes a specified number of hosts matching these criteria.

Added commandline switch "preferred_archs", which takes a list of architectures
that will be used as preferred architectures in host_conf_get_suited_hosts,
unless preferred architectures are specified in the function call to

Change History (0)

Note: See TracTickets for help on using tickets.