DYNES-Deployments

["David A. J. Ripley" <>]

Hi Jim,

Once you've taken a look a the docs, if there are things you need assistance 
with and/or you have specific questions, if you email 

 it will open a ticket and we can help you with any hurdles you encounter.

D.
--
David A. J. Ripley, Systems Engineer
Indiana University GlobalNOC.
<>
 +1-812-855-5079
http://mypage.iu.edu/~daripley/daripley.pgp

On Apr 18, 2013, at 11:37 AM, "Barr, James" 
<>
 wrote:

> Let us look at this doc again.
> 
> Thanks,
> JB
> 
> -----Original Message-----
> From: 
> 
>  
> [mailto:]
>  On Behalf Of Benjeman Meekhof
> Sent: Thursday, April 18, 2013 11:36 AM
> To: 
> 
> Cc: Gray, Charles
> Subject: Re: [dynes-deployments] Administrator Configuration Checklist
> 
> At one time after a call with Tufts I was asked to sent the collection of 
> dynes documentation containing user and password information to 
> .
>   Do you have this documentation?  If so, please see the document 
> DYNES_README for information on setting up accounts on the FDT or IDC 
> server.  Please see the document dynes-switch-config-tufts.docs.pdf for 
> information on logging into the switch.  You may create any new accounts or 
> change the password on any "admin" account but we ask you do not alter the 
> "dynes" account in any way.
> 
> Please be aware, as also noted in the documents, you cannot log into the 
> FDT or IDC machines with a password over ssh.  It is required that you 
> setup an ssh key-based login via local console access.  This is documented 
> in the aforementioned readme.
> 
> If there are any questions about this documentation, or you do not have the 
> documentation, please let me know.  Because it contains default password 
> information (which should be changed) we prefer not to post it publicly but 
> I can send it to you directly.
> 
> 
> regards,
> Ben
> 
> On Thu, Apr 18, 2013 at 10:48 AM, Barr, James 
> <>
>  wrote:
>> So, the frustration here is that we are continually referred back to the 
>> DYNES doc links.
>> Am I to understand that nobody can assist us with basic user setup and 
>> operation? I am trying to get a final determination on this so I can 
>> inform our senior management (so we can try to assign priority on this 
>> project and get an estimate of hours required to make it work).
>> 
>> Thanks,
>> JB
>> 
>> -----Original Message-----
>> From: 
>> 
>>  
>> [mailto:]
>>  On Behalf Of Dale W. 
>> Carder
>> Sent: Thursday, April 18, 2013 10:41 AM
>> To: 
>> 
>> Cc: Gray, Charles
>> Subject: Re: [dynes-deployments] Administrator Configuration Checklist
>> 
>> 
>> Hi Jim,
>> 
>> You can find a lot of documentation here:
>> http://www.internet2.edu/ion/dynes.html  (scroll down) 
>> https://spaces.internet2.edu/display/dynesdoc/Home
>> http://www.internet2.edu/ion/docs/FDTAgent_Usage_Dynes_v03.pdf
>> 
>> In a nutshell, the boxes are more or less yours to maintain.  See the FAQ 
>> for more details / caveats.
>> 
>> In the documentation for the FDT there is a "dynes ping" sort of command 
>> you can use in addition to file transfer tools.
>> 
>> For local passwords, this would have been chosen as part of the 
>> provisioning for your site.  The dynes admins can probably use their 
>> backdoor and reset it for you.  Then you can log in as root on console and 
>> set up local user accounts (and corresponding ssh keys) or do whatever it 
>> is that your site does.
>> 
>> Dale
>> 
>> Thus spake Barr, James 
>> ()
>>  on Thu, Apr 18, 2013 at 12:56:20PM +0000:
>>> Hi Brian,
>>> 
>>> More practically, I have questions about DYNES as a service that don't 
>>> seem to have an answer from any of our folks internally:
>>> 
>>> 1) How does one obtain an account on the DYNES server and begin using 
>>> Dynes?
>>> 2) Will the  accounts be LDAP enabled or is it a local account that must 
>>> be setup on the server?
>>> 
>>> Forgive me, the individual who was lead on this left back in February and 
>>> this project got passed to my department (enterprise infrastructure).
>>> Our network team was instrumental in getting the DYNES equipment on line, 
>>> but they would not be the ones who will administrate the system and 
>>> assist with user logins, file transfers, general questions, etc.
>>> 
>>> Is there a step by step admin guide we can use (as in, step 1, login to 
>>> the VM on the DYNES physical host, setup a user, test functionality, 
>>> confirm data transfer is working, etc)?
>>> This would provide the best way for us to wrap a service around the 
>>> product and create and modify internal docs that any of my admins can use.
>>> 
>>> Some of the links in the DYNES documentation wiki are dead, or lead to 
>>> other projects (OSCARS, for example) which are used, but not specific to 
>>> DYNES.
>>> 
>>> Any help you can provide would be appreciated.
>>> 
>>> Thanks,
>>> 
>>> Jim Barr
>>> Manager, Enterprise Infrastructure
>>> Tufts University
>>> 617-627-0657
>>> 
>>> 
>>> -----Original Message-----
>>> From: 
>>> 
>>> [mailto:]
>>>  On Behalf Of Brian 
>>> Cashman
>>> Sent: Thursday, April 18, 2013 8:09 AM
>>> To: Gray, Charles
>>> Cc: 
>>> 
>>> Subject: Re: [dynes-deployments] Administrator Configuration 
>>> Checklist
>>> 
>>> Charles,
>>> 
>>> No one here knows of a specific checklist. Is there any more detail you 
>>> can provide?
>>> 
>>> Thanks,
>>>      Brian Cashman
>>>      Internet2
>>> 
>>> On 4/16/13 4:09 PM, 
>>> 
>>>  wrote:
>>>> Someone here at Tufts has asked "Has the administrator 
>>>> configuration check list already been done for our site?"
>>>> 
>>>> Could you please refer me specifically to that document?  There's 
>>>> much documentation to wade through and wiki search isn't fruitful 
>>>> on the terms "configuration checklist"
>>>> 
>>>> Regards,
>>>> Charles Gray
>>>> Senior Systems Administrator
>>>> Tufts Technology Services (TTS)
>>>> 169 Holland Street
>>>> Somerville, MA 02144
>>>> (617) 627-5327 (w)
>>>> (617) 627-3307 (f)
>>>> it.tufts.edu
>>>> 
>>> 
>>>