Opened 15 years ago

Last modified 10 years ago

#316 new enhancement

IZ1952: cluster-hosts like cluster-queues for easy exec host management

Reported by: reuti Owned by:
Priority: normal Milestone:
Component: sge Version: 6.0u7
Severity: Keywords: kernel


[Imported from gridengine issuezilla]

        Issue #:      1952             Platform:     All           Reporter: reuti (reuti)
       Component:     gridengine          OS:        All
     Subcomponent:    kernel           Version:      6.0u7            CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    ENHANCEMENT
                                   Target milestone: ---
      Assigned to:    andreas (andreas)
      QA Contact:     andreas
       * Summary:     cluster-hosts like cluster-queues for easy exec host management
   Status whiteboard:

     Issue 1952 blocks:
   Votes for issue 1952:

   Opened: Thu Dec 22 13:50:00 -0700 2005 

For now each exec host needs an entry on it's own, and changing some attached complex_values
means a loop across all the involved nodes. Having some kind of cluster-host in the way like now
cluster-queues are present in 6.0, would make administration a lot easier.

Each cluster-host would need a definition of the attached exec hosts (or hostgroups) and each exec
host has to be attached to exactly one cluster-host. This way the current behavior could simply be
implemented by attaching only one exec host to one cluster host (similar to cluster-queues).

The commands qconf -ae,-de would be like qconf -as,-ds only to make the exec host known to SGE.

The cluster-host definition could include definitions like:

complex_values  virtual_free=2G,[@bigones=virtual_free=4G]

which is similar to cluster-queues. Possibly the qconf -aconf,... stuff may also be included here.

   ------- Additional comments from reuti Mon Dec 26 03:52:45 -0700 2005 -------
To put the configuration also in this entry, a new special value "INHERIT" might be useful, which allows to
keep the global configuration for this parameter. E.g.:

mailer inherit,[@custom_ones=/opt/mail]

   ------- Additional comments from reuti Thu Oct 9 03:09:32 -0700 2008 -------
Instead of having this special entry 'inherit', one and only one configuration might be more straight
forward. Entries without a host/hostgroup are global ones. Others are just for the mentioned

Change History (0)

Note: See TracTickets for help on using tickets.