----- Original Message -----
From: Dimitri Nilsen <[log in to unmask]>
Date: Monday, May 12, 2014 3:54 pm
Subject: Re: [LCG-ROLLOUT] GLUE2ComputingShareMax* values by creamce
> Hi Goncalo,
>
> thanks, its my fault, I overlooked the difference.
>
> But then my question is, how and where to configure proper
> GLUE2ComputingShareDefault* values?
this issue has been recently reported [1] and it will be
tracked within the next ge-utils release.
[1] https://ggus.eu/?mode=ticket_info&ticket_id=104815
>
> Regards
> Dimitri
>
> On 12.05.2014 12:40, Gonçalo Borges wrote:
> > Hi Dimitry...
> >
> > These are different fields. One is
> >
> > GLUE2ComputingShare*Default*WallTime
> >
> > and another is
> >
> > GLUE2ComputingShare*Max*WallTime
> >
> > The GE infoprovider is not production any value for the
> > GLUE2ComputingShare*Default*WallTime, and that is why it is '999999'
> >
> > Cheers
> > Goncalo
> >
> > On 05/12/2014 10:23 AM, Dimitri Nilsen wrote:
> >> Hi,
> >>
> >> we are facing the problem that GLUE2ComputingShareMax*
> parameters are
> >> not showing in bdii output properly. By running ldapsearch to
> the
> >> CREAM_CE we always get default values:
> >>
> >> ldapsearch -xLLL -b o=glue -p 2170 -h cream-ge-1-kit | grep
> >> GLUE2ComputingShareDefaultWallTime
> >> GLUE2ComputingShareDefaultWallTime: 999999999
> >> GLUE2ComputingShareDefaultWallTime: 999999999
> >> GLUE2ComputingShareDefaultWallTime: 999999999
> >>
> >> however on the CREAM itself running provider scripts seems to be
> fine:>> /usr/libexec/glite-info-dynamic-ge --info -c
> /etc/lrms/scheduler.conf>> dn:
> >> GLUE2ShareID=sl6_ops_cream-ge-1-
> kit.gridka.de_ComputingElement,GLUE2ServiceID=cream-ge-1-
> kit.gridka.de_ComputingElement,GLUE2GroupID=resource,o=glue>>
> GLUE2ComputingShareMaxRunningJobs: 29424
> >> GLUE2ComputingShareMaxCPUTime: 432000
> >> GLUE2ComputingShareMaxWallTime: 432000
> >> GLUE2ComputingShareServingState: Production
> >> ..
> >>
> >> and
> >> cat /var/lib/bdii/gip/plugin/glite-info-dynamic-ce
> >> #!/bin/sh
> >> /usr/libexec/glite-ce-check-submission-state
> >> /etc/glite-ce-dbtool/creamdb_min_access.conf
> >> retcode=$?
> >> if [ $retcode = 1 ] || [ $retcode = 2 ] ; then
> >> # Submissions disabled. Publish Draining
> >> /usr/libexec/glite-info-dynamic-ge --info -c
> >> /etc/lrms/scheduler.conf | sed -e 's/GlueCEStateStatus:
> >> Production/GlueCEStateStatus: Draining/'
> >> else
> >> # Submissions enabled. The default cluster.state will be used
> >> /usr/libexec/glite-info-dynamic-ge --info -c
> /etc/lrms/scheduler.conf>> fi
> >>
> >>
> >> so what could the problem that bdii does not take right values
> from
> >> provider scripts?
> >>
> >> Regards
> >> Dimitri
> >>
> >
>
>
> --
> Dimitri Nilsen, Dipl.-Ing(FH)
>
> Karlsruhe Institute of Technology (KIT)
> Steinbuch Centre for Computing
> Kaiserstr. 12
> 76131 Karlsruhe, Germany
>
> Tel.: +49 721 608 28607
> Email: [log in to unmask]
>
>
|