[Swift-devel] Tool for TeraGrid site info

[Glen Hocky]

yes that is what it does...i was just lazy but there are other better 
ways, certainly

Michael Wilde wrote:
> Glen, I re-read your mail and realize maybe I misunderstood. When you 
> said "my script downloads their tool for querying info.teragrid" did 
> you mean that tgsites first dynamically downloads the tg info tool, 
> and then runs it, unmodified?
>
> If so, that seems perhaps not the best technical solution, but as long 
> as the tg tool is not placed into svn and is not redistributed by us, 
> using it by downloading seems to me to not have any licensing issues, 
> and I would go ahead and start with whatever is working as the base 
> version to build on and improve.
>
> - Mike
>
>
> On 5/13/09 1:48 PM, Michael Wilde wrote:
>> I think its best if we do not copy the tg tool. I dont think there 
>> are any licensing issue with using the tg sites info tool, but 
>> certainly are issues with putting it into the swift source tree and 
>> hence re-distributing it. We definitely do not want to do the latter.
>>
>> Dependencies on the format of the tool we should live with, and adapt 
>> our code as needed.  I think we want to use, e.g., the REST 
>> interface, which I would hope they either seldom change, or they 
>> attempt to keep changes to it backwards compatible.
>>
>> - Mike
>>
>>
>> On 5/13/09 1:33 PM, Glen Hocky wrote:
>>> I'm ok with contributing my code. One thing to note though is rather 
>>> than using the info as posted on info.teragrid, my script downloads 
>>> their tool for querying info.teragrid. I did this because I was 
>>> hoping that their tool would keep a uniform formatting whereas the 
>>> back-end might change.
>>>
>>> There could however be licensing issues with this usage of their 
>>> tool....
>>>
>>> Michael Wilde wrote:
>>>>
>>>>
>>>> On 5/13/09 12:44 PM, skenny at uchicago.edu wrote:
>>>>> hey ben,
>>>>>
>>>>> we are looking at using glen's code as a starting point for a
>>>>> tool that could be included in swift/committed to swift's svn.
>>>>> there will need to be quite a bit of testing first as i'm
>>>>> unsure about committing someone else's code 'as is'
>>>>
>>>> If Glen agrees to contribute the code (by signing the license), 
>>>> then I think you should commit his exact code as the initial 
>>>> revision, and edit from there.
>>>>
>>>> - Mike
>>>>
>>>> ...however,
>>>>> my other question regarding this is that there is apparently
>>>>> some *paperwork* involved in this process which would require
>>>>> me (and glen?) to sign some sort of globus licensing agreement
>>>>> (?)
>>>>> i'm unsure of the specifics but could you let me know the best
>>>>> way to get the ball rolling?
>>>>>
>>>>> thanks
>>>>> ~sarah
>>>>>
>>>>>
>>>>> ---- Original message ----
>>>>>> Date: Wed, 29 Apr 2009 11:10:14 -0500
>>>>>> From: Michael Wilde <wilde at mcs.anl.gov>  Subject: [Swift-devel] 
>>>>>> Tool for TeraGrid site info  To: Glen Hocky 
>>>>>> <hockyg at uchicago.edu>, swift-devel
>>>>> <swift-devel at ci.uchicago.edu>
>>>>>> Glen, where is the latest version of your TG sites info tool?
>>>>>>
>>>>>> Ben, what should we do to start testing that, making it
>>>>> uniform with the
>>>>>> osg tool, and make it available for comments and heading towards 
>>>>>> inclusion in Swift?
>>>>>>
>>>>>> (I think this was commented on earlier - I will track down
>>>>> when I get
>>>>>> back to the planning list in a few days from now)
>>>>>> _______________________________________________
>>>>>> Swift-devel mailing list
>>>>>> Swift-devel at ci.uchicago.edu
>>>>>> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>>>
>> _______________________________________________
>> Swift-devel mailing list
>> Swift-devel at ci.uchicago.edu
>> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel