Hi List,
>>> 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.
As I moved the GridICE collector from the SE to the MON node with the
upgrade last week, I can confirm that the service is not published in the
infosys. I need to include the corresponding entry in one of the GRISes -
my old one from 2_4_0 looks like this:
dn: GlueServiceURI=ldap://grid100.kfki.hu:2136,mds-vo-name=BUDAPEST,o=grid
objectClass: GlueService
objectClass: GlueSchemaVersion
GlueServiceURI: ldap://grid100.kfki.hu:2136
GlueServiceAccessPointURL:
ldap://grid100.kfki.hu:2136/mds-vo-name=local,o=grid
GlueServiceType: gridice
GlueServicePrimaryOwnerName: LCG
GlueServicePrimaryOwnerContact: [log in to unmask]
GlueServiceHostingOrganization: BUDAPEST
GlueServiceMajorVersion: 1
GlueServiceMinorVersion: 1
GlueServicePatchVersion: 1
GlueServiceAccessControlRule: atlas
GlueServiceAccessControlRule: alice
GlueServiceAccessControlRule: lhcb
GlueServiceAccessControlRule: cms
GlueServiceAccessControlRule: dteam
GlueServiceAccessControlRule: hungrid
GlueServiceInformationServiceURL:
ldap://grid100.kfki.hu:2135/mds-vo-name=local,o=grid
GlueServiceStatus: running
GlueSchemaVersionMajor: 1
GlueSchemaVersionMinor: 1
can I use this with obvious modifications, or has this part of the schema
changed with the new release?
Thanks,
Szabolcs
>>>
>>> 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
>>>>>
>>>
>>>
>>
>
>
> --
> ---
> Cristina Aiftimiei - EGEE Project
> Ist. Naz. di Fisica Nucleare - Padova
> Address: via F. Marzolo, 8 - 35131 Padova - ITALY Email:
> [log in to unmask]
> Phone: +39-0498277005
> Mobile:+39-3460230488
>
|