Hi Laurence,
Laurence Field wrote:
> The reason for this decision was to make things more uniform.
>
> MON in this case is short for Monitoring. Previous to LCG-2_6_0, this
> only contained the R-GMA server. However, it would makes sense to move
> the GridIce server here too and reduce the load on the SE. This will
> give us a more uniform structure.
> CE is the interface to the batch system.
> SE is the interface to the storage system.
> MON is the interface to the monitoring system.
just to double-check, please verify that there is still a "standard"
GRIS (CE/SE) publishing the existence of the GridICE collector (alias
the GRIS started by gridice-mds) by using the GlueService entry.
Until now, the two GRIS's were running on the same machine. I don't
remember if there is any dependency on the configuration process.
Cheers, Sergio
>
> The default Yaim configuration now does this, however as usual it is up
> to sites to choose. Some sites will run all services on one node,
> others run them on separates nodes. An example is the site BDII. By
> default this is installed on the CE but some sites chose to install it
> on a separate node.
>
>
> Laurence
>
>
> Dan Schrager wrote:
>
>> Hi YAIM authors,
>>
>> I have noticed that yaim 2.4.0 sets by default
>> GRIDICE_SERVER_HOST=$SE_HOST while the latest yaim 2.6.0 sets it to
>> GRIDICE_SERVER_HOST=$MON_HOST (in file site-info.def).
>>
>> Does it matter ?
>> Should I move the gridice service to the $MON_HOST and terminate it on
>> the $SE_HOST ? Which rpms should be erased from the $SE_HOST, related
>> exclusively to this service ? Does YAIM automagically do this work
>> during install and configure (at least it stops permanently the
>> related services ?)
>> Should I leave it on the $SE_HOST ?
>>
>> Regards,
>> Dan
>>
--
Sergio Andreozzi
INFN-CNAF, Tel: +39 051 609 2860
Viale Berti Pichat, 6/2 Fax: +39 051 609 2746
40126 Bologna (Italy) Web: http://www.cnaf.infn.it/~sergio
|