Project

General

Profile

Bug #23339

Make wholenode knobs uniform

Added by Marco Mascheroni about 2 months ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Category:
-
Target version:
Start date:
09/26/2019
Due date:
% Done:

0%

Estimated time:
First Occurred:
Occurs In:
Stakeholders:

Factory Ops

Duration:

Description

Right now the way to set up a whole node entry is the following:

           <attr name="GLIDEIN_CPUS" const="True" glidein_publish="False" job_publish="True" parameter="True" publish="True" type="string" value="auto"/>
            <attr name="GLIDEIN_ESTIMATED_CPUS" const="True" glidein_publish="False" job_publish="True" parameter="True" publish="True" type="string" value="8"/>
            <attr name="GLIDEIN_MaxMemMBs" const="True" glidein_publish="True" job_publish="False" parameter="True" publish="True" type="string" value=""/>
            <attr name="GLIDEIN_MaxMemMBs_Estimate" const="True" glidein_publish="True" job_publish="False" parameter="True" publish="True" type="string" value="True"/>

In particular, if GLIDEIN_MaxMemMBs is set it takes the precedence over the estimation and we use that value. So, in the production factory it has to be set to an empty string because the attribute has a global default value of 2500.
Also, the GLIDEIN_MaxMemMBs/GLIDEIN_MaxMemMBs_Estimate has a different semantics compared to GLIDEIN_CPUS/GLIDEIN_ESTIMATED_CPUS.

I susggest to we use GLIDEIN_MaxMemMBs=auto to enable the estimation, and then use GLIDEIN_MaxMemMBs_Estimate in order to provide an estimation of the memory for the frontend matchmaking (which we will need to implement!).

History

#1 Updated by Marco Mascheroni about 2 months ago

  • Stakeholders updated (diff)


Also available in: Atom PDF