Opened 14 years ago

Last modified 10 years ago

#987 new enhancement

IZ46: testsuite commandline option "zones"

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


[Imported from gridengine issuezilla]

        Issue #:      46              Platform:     All           Reporter: joga (joga)
       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 commandline option "zones"
   Status whiteboard:

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

   Opened: Wed Nov 15 02:41:00 -0700 2006 

It is possible to configure Solaris zones for a host listed in the testsuite
host configuration.

If zones are configured, the zones will be used. Testsuite will install these
zones as execution hosts.

As zones are always used as soon as they are configured for a host, it is
necessary to have 2 testsuite host configurations - one with and one without zones.

Better would be to have one testsuite host configuration listing all zones, and
specifying on the commandline if we want to use the zones or not.

An enhanced variant of this zones parameter would be to give it the number of
zones to use per host.
By this, we could for example configure 10 zones for each host, but make
testsuite use only a maximum of e.g. 5 of these zones (per host).

   ------- Additional comments from joga Thu Mar 1 02:56:16 -0700 2007 -------
Some additional ideas:
Arguments for the zones option:
1..n: specifies the maximum number of zones per host
all: use all zones configured per host

And currently, if zones are configured for a host, testsuite will install
execution daemons only on the zones, but not on the host itself.
We might want to have an option to control this behaviour, something like

Change History (0)

Note: See TracTickets for help on using tickets.