Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

Community discussion is located here: http://community.pbspro.org/t/pp-719-enhance-setup-in-ptl-specifically-for-cray-platforms/463


Overview:

PBSTestSuite.setUp() calls several functions. The changes made in the settings in these functions are often not desirable on Cray because the MoM, scheduler, and server settings get reverted to plain Linux out-of-box configurations.


Out-of-box configuration of PBS on Cray:

  • PBS is installed and configured on Cray which result in specific settings. These initial settings are referred to as the out-of-box settings below.  These settings should also apply to the Cray ALPS simulator when PBS is properly configured.  These are settings for a freshly installed and configured PBS on Cray or Cray ALPS simulator.

  • As of current support for Cray CLE 5.2 and 6.0, below are the out-of-box configuration settings per PBS daemon:

1)  MoM

    • These lines should appear in PBS_HOME/mom_priv/config:
    •         $vnodedef_additive 0
    •         $alps_client <path to ALPS API>
    •         $usecp *:/home /home

      Notes: $usecp setting above is used to enable local copy of job output of jobs that ran on compute nodes.
      $vnodedef_additive 0 will allow MoM to tell the server that there are vnodes missing, which the server will mark as stale.

2) Scheduler

    • PBS_HOME/sched_priv/sched_config will have 'vntype' in the resources line.

3) Server

    • The hook PBS_HOME/server_priv/hooks/PBS_translate_mpp.HK is enabled.
    • Based on what is returned by the ALPS inventory :
      • vnodes representing the compute nodes will get created
      • the Cray-specific custom resources (e.g. PBScraynid, PBScrayhost, etc) will get created in PBS_HOME/server_priv/resourcedef.
      • the appropriate Cray-specific custom resources will be added to the vnodes.
      • since the mom config $vnode_per_numa_node is unset by default, there will be no PBScrayseg attribute on the vnodes representing the compute nodes.
    • Server settings :
      • flatuid = true

      • scheduling = true

      • the default queue is workq


Interface:  MoM.__init__() 

  • Visibility: Public
  • Change Control: Stable
  • Synopsis: Modifications to include initial MoM config settings for Cray.
  • Standing of the interface : modified interface
  • Details
    • if on real Cray or Cray ALPS simulator, then initialize the PBS_HOME/mom_priv/config to have these:

    • $vnodedef_additive 0

    • $alps_client <path to ALPS API>

    • $usecp *:/home /home


Interface:  Scheduler.revert_to_defaults() 

  • Visibility: Public
  • Change Control: Stable
  • Synopsis: Modifications to include 'vntype' in sched_config out-of-box settings for Cray.
  • Standing of the interface : modified interface
  • Details
    • After copying the out-of-box scheduler configuration in PBS_EXEC/etc/pbs_sched_config to PBS_HOME/sched_priv/sched_config :
      • If platform is a real Cray or Cray ALPS simulator, then add "vntype" to resources line of PBS_HOME/sched_priv/sched_config.


Interface:  Server.revert_to_defaults() 

  • Visibility: Public
  • Change Control: Stable
  • Synopsis: Modifications to revert resources, vnodes, and hooks settings for Cray.
  • Standing of the interface : modified interface
  • Details
  • resources and vnodes
    • As part of reverting resources, the PBS_HOME/server_priv/resourcedef file is removed.
      • If on Cray or Cray ALPS simulator, then recreate the out-of-box Cray-specific custom resources and vnodes,
        including the ones PBS creates from reading the ALPS inventory, by:
        • Checking that $alps_client and its value exists in PBS_HOME/mom_priv/config, and if so:
          • delete all the vnodes: qmgr -c "delete node @default"
          • add back the MoMs: qmgr -c "create n <MoM hostname>"
          • check until such time that the MoM node has actually been added and the node state is free
          • if successful, then
            • the resourcedef file and the vnodes would have reverted to the out-of-box Cray configuration.
          • If there is an error during one of the following:
            • checking if $alps_client is properly configured
            • deleting all vnodes
            • adding MoMs
            then raise an exception.


  • No labels