Print

Print


P.S.

Any problems with things like this should be dicussed on the Glue Schema
list mailto:[log in to unmask] and taken off the Rollout list.


Laurence wrote:

> Hi Jeff,
>
> This has been discussed at length before on the Rollout list and we
> don't want to go round in circles. The last thread that was on the
> rollout list was used as input for dicussing this during the Glue Schema
> meeting.  The outcome come was that these values should be defined as
> Steve T mentioned.
>
> lsb_release -d
>
> Description:    Scientific Linux SL Release 3.0.3 (SL)
>
> Would translate as
>
> GlueHostOperatingSystemName: Scientific Linux SL
> GlueHostOperatingSystemRelease: 3.0.3
> GlueHostOperatingSystemVersion: SL
>
>
> These attibutes are "higher level management" attributes and should not
> be use by experiments in the jdls.
>
>
> Jeff Templon wrote:
>
>> Hi,
>>
>> I can't find it.  Err, I *can* find the document, but I can't find any
>> hint of a standard approach to defining the values -- the attributes are
>> mentioned in the draft, but there is no discussion of what values are
>> good or bad.  I also noticed that there were no units on the ETT values;
>> I hope somewhere the units are defined.  It would be worth putting them
>> there anyway.
>>
>> Thanks
>>
>>                        JT
>>
>> Laurence wrote:
>>
>>> Glue Schema draft
>>> http://infnforge.cnaf.infn.it/docman/view.php/9/90/GLUEInfoModel_1_2_draft_7.pdf
>>>
>>>
>>>
>>>
>>> Jeff Templon wrote:
>>>
>>>> Can someone send me the proposal?  It sounds like a bad one.  The
>>>> users
>>>> will not be able to easily write JDLs that select all Enterprise-Linux
>>>> compatible systems.  It'll need to be a big damn OR of all possible
>>>> flavors.  Ugh.  Ptoei.
>>>>
>>>> Plus it encourages people to pretend ... i know some people who almost
>>>> put "SLC" in the info, even though they weren't running SLC ...
>>>> this is
>>>> because some people match on all SLC sites, so SLC would stand for
>>>> Scientific Linux Compatible in this case.  We have enough pretending,
>>>> let's not start it here too.
>>>>
>>>>                                JT
>>>>
>>>> ps nice slip, in the "daft" for new schema version ;-)
>>>>
>>>> Laurence wrote:
>>>>
>>>>> This proposal is in the daft for the new schema version 1.2.
>>>>>
>>>>> Steve Traylen wrote:
>>>>>
>>>>>> On Thu, Apr 14, 2005 at 05:10:04PM +0200 or thereabouts, Debreczeni
>>>>>> Gergely wrote:
>>>>>>
>>>>>>
>>>>>>> Hi !
>>>>>>>
>>>>>>> Users are complainig - when they put OS requirements into their
>>>>>>> jdl file - that apparently there is no LCG-wide agreement on
>>>>>>> OS naming conventions. Indeed, a quick survey gives the result
>>>>>>> below. Should we somehow define the possible OS names ?
>>>>>>> May there was already a discussion about this issue ?
>>>>>>> thanks,
>>>>>>> Gergely
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> People have tried, no one can agree.
>>>>>>
>>>>>> Using
>>>>>>
>>>>>> lsb_release -d
>>>>>>
>>>>>> is the favourite though (well at least mine).
>>>>>>
>>>>>> There is even features in gstat to police peoples setting once
>>>>>> agreement
>>>>>> is made.
>>>>>>
>>>>>> For me this shows
>>>>>>
>>>>>> Description:    Scientific Linux SL Release 3.0.3 (SL)
>>>>>>
>>>>>> which could translate as
>>>>>>
>>>>>> GlueHostOperatingSystemName: Scientific Linux SL
>>>>>> GlueHostOperatingSystemRelease: 3.0.3
>>>>>> GlueHostOperatingSystemVersion: SL
>>>>>>
>>>>>> but that is open.
>>>>>>
>>>>>>  Steve
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> ldapsearch -x -H ldap://site-bdii.some.where:2170 -b \
>>>>>>> mds-vo-name=sitename,o=grid  | grep -i GlueHostOperatingSystemName
>>>>>>>
>>>>>>>
>>>>>>> GlueHostOperatingSystemName: Redhat
>>>>>>> GlueHostOperatingSystemName: Redhat
>>>>>>> Could not create LDAP session handle (3): Time limit exceeded
>>>>>>> GlueHostOperatingSystemName: Redhat
>>>>>>> ldap_bind: Can't contact LDAP server
>>>>>>> GlueHostOperatingSystemName: Redhat
>>>>>>> GlueHostOperatingSystemName: Scientific Linux
>>>>>>> GlueHostOperatingSystemName: SL
>>>>>>> GlueHostOperatingSystemName: Redhat
>>>>>>> GlueHostOperatingSystemName: Redhat
>>>>>>> GlueHostOperatingSystemName: SL
>>>>>>> GlueHostOperatingSystemName: Redhat
>>>>>>> GlueHostOperatingSystemName: Redhat
>>>>>>> GlueHostOperatingSystemName: Redhat
>>>>>>> ldap_bind: Can't contact LDAP server
>>>>>>> GlueHostOperatingSystemName: Redhat
>>>>>>> GlueHostOperatingSystemName: Redhat
>>>>>>> GlueHostOperatingSystemName: ScientificLinux
>>>>>>> GlueHostOperatingSystemName: Scientific
>>>>>>> GlueHostOperatingSystemName: SL
>>>>>>> GlueHostOperatingSystemName: Redhat
>>>>>>> GlueHostOperatingSystemName: SL
>>>>>>> GlueHostOperatingSystemName: Redhat
>>>>>>> GlueHostOperatingSystemName: Redhat
>>>>>>> GlueHostOperatingSystemName: SL
>>>>>>> GlueHostOperatingSystemName: SLC
>>>>>>> GlueHostOperatingSystemName: Redhat
>>>>>>> GlueHostOperatingSystemName: SL
>>>>>>> GlueHostOperatingSystemName: SL
>>>>>>> GlueHostOperatingSystemName: Scientific Linux
>>>>>>> GlueHostOperatingSystemName: Redhat
>>>>>>> GlueHostOperatingSystemName: Redhat
>>>>>>> GlueHostOperatingSystemName: Redhat
>>>>>>> ldap_bind: Can't contact LDAP server
>>>>>>> ldap_bind: Can't contact LDAP server
>>>>>>> GlueHostOperatingSystemName: Redhat
>>>>>>> GlueHostOperatingSystemName: Redhat
>>>>>>> GlueHostOperatingSystemName: Redhat
>>>>>>> ldap_bind: Can't contact LDAP server
>>>>>>> GlueHostOperatingSystemName: SL
>>>>>>> GlueHostOperatingSystemName: Redhat
>>>>>>> lueHostOperatingSystemName: Redhat
>>>>>>> GlueHostOperatingSystemName: SLC
>>>>>>> GlueHostOperatingSystemName: Redhat
>>>>>>> GlueHostOperatingSystemName: SLC
>>>>>>> GlueHostOperatingSystemName: Redhat
>>>>>>> ldap_bind: Can't contact LDAP server
>>>>>>> GlueHostOperatingSystemName: SLC
>>>>>>> GlueHostOperatingSystemName: RedHat
>>>>>>> GlueHostOperatingSystemName: SL
>>>>>>> GlueHostOperatingSystemName: SL
>>>>>>> GlueHostOperatingSystemName: SLC
>>>>>>> GlueHostOperatingSystemName: Scientific
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> Steve Traylen
>>>>>> [log in to unmask]
>>>>>> http://www.gridpp.ac.uk/
>>>>>>
>>>>>>