DYNES-Deployments

[Jason Zurawski <>]

Hi Wilson;

Contact 

 and we will work with Dell for now.  Before Aug 2013 we will pass the 
information to the schools regarding warranty support.  

Thanks;

-jason

On Oct 23, 2012, at 3:12 PM, "Dillaway, Wilson" 
<>
 wrote:

> Jason,
>     And a separate unrelated question:
> 
> If in the future we experience an FDT or IDC Dell server hardware failure 
> (bad memory, hard disk, etc.), should we call Dell, or is that to be 
> handled through Internet2 or the supporting universities?
> 
>               Thanks!
> 
>                      Wilson
> 
> 
> -----Original Message-----
> From: Jason Zurawski 
> [mailto:]
>  
> Sent: Tuesday, October 23, 2012 4:18 PM
> To: Dillaway, Wilson
> Cc: Brian Cashman; 
> ;
>  Eric Boyd
> Subject: Re: Question about web or API access to DYNES capability
> 
> Hi Wilson;
> 
> Since this is a topic that is better seen by the entire community, I am 
> placing it on the mailing list.  
> 
> Brian Cashman (CCed) is putting together documentation to address just what 
> you ask in a more complete manner.  There is some out there now on the 
> OSCARS API and web interface but this may be a little raw for the 
> unexperienced (e.g. developer documentation written by developers):
> 
> - Full protocol specification for writing web service queries: 
> http://www.controlplane.net
> 
> - OSCARS web interface information: 
> https://oscars.es.net/OSCARS/docs/UserManual.html
> 
> With regards to ATLAS, others afflicted with the project and on this list 
> will be able to comment more.  I would also encourage you to mail 
> 
>  (join here: https://listserv.es.net/mailman/listinfo/oscars-users) with 
> additional questions.  The developers are on this list, and are better 
> geared to support questions of this nature.  
> 
> Hope this helps;
> 
> -jason
> 
> On Oct 23, 2012, at 2:03 PM, "Dillaway, Wilson" 
> <>
>  wrote:
> 
>> Jason and others,
>>     I am responding to the following email:
>> 
>> ========================================================
>>> 
>>> From: Jason Zurawski 
>>> <>
>>> Date: July 27, 2012 7:58:48 PM EDT
>>> To: 
>>> 
>>> Subject: [dynes-deployments] FDT Documentation All;
>>> 
>>> We would like to note the availability of new documentation describing 
>>> use of the FDT tool:
>>> 
>>> http://www.internet2.edu/ion/docs/FDTAgent_Usage_Dynes_v01.pdf
>>> 
>>> This should be passed along to users on your campus.  Please let us know 
>>> of questions/comments.
>>> 
>>> Thanks;
>>> 
>>> -jason
>>> 
>> ========================================================
>> 
>>     Thank you for the helpful document (I have now fetched version 3 from 
>> the Internet2 web site).  Among other things, it describes how to make FDT 
>> requests from the Linux command line.
>> 
>> 
>> And a question.  There is a two-page PDF (dated July 7, 2011) on the 
>> Internet2 web site as follows:
>> http://www.internet2.edu/pubs/201107-IS-DY.pdf
>> 
>> which contains the following diagram:
>> 
>> <image002.jpg>
>>     My question is regarding the two "API Request" entities in the 
>> diagram, namely the web page and the application.  Do these exist, as 
>> samples, in a form available to the DYNES community?  My reason for asking 
>> is two-fold:
>> 
>> 1.)    For a certain category of DYNES user, making an FDT request from a 
>> web page might be more attractive than from the Linux command line.
>> 
>> 2.)    As regards an application calling the API, Tufts is an LHC/ATLAS 
>> Tier3 site, and that will be our primary and earliest use case for DYNES.  
>> Has any of the ATLAS software suite been modified to make its own API 
>> calls to absorb the function of the FDT server, such that files can be 
>> moved via DYNES directly from the ATLAS toolset without using the FDT 
>> command line directly?
>> 
>> 
>>                          Thanks!
>> 
>> 
>>                              Wilson Dillaway
>>                              Infrastructure Planning
>>                             Tufts University
>>                             
>>