Distributed Computing Task Force: "Files" Working Group" 11/1/95 Meeting

Agenda

• A little history...
• Current ISC strategies...
• Why bother?
• Considerations for the future...

Current ISC strategies

• PennNet (via DCCS maintained file servers):
  • TCP/IP (ftp.upenn.edu)
    • Network Applications for Macs and PCs
    • Files (some documentation)
    • Access Method
      • Authenticated FTP (PennNet ID/Passwored)
      • anonymous FTP (anonymous/email address)
  • AppleTalk (Penn_Software):
    • Network Applications with helper apps.
    • Access Method:

      		Zone:		UPENN-ISC-DCCS
      		Server:		Penn_Software
      		User:		Penn
      		Password:	Penn
      		Volume:		Penn_Software

    • IPX (in planning - pending completion of IPX routing)

• SneakerNet (via CRC distributed diskettes):
  • MacOS:
    • PPP for Macintosh (1 disk)
      • MacSLIP v3.02 (w PPP support)
      • MacTCP v2.06
    • Network Applications Installer (1 disk)
      • Fetch v2.1.2
      • NCSA Telnet v2.7b4
      • Netscape v1.12 with helper appls (Stuffit Expander, Sound Machine)
    • AppleTalk patches
  • Windows v3.x:
    • PPP for Windows (3 disks)
      • Custom Installer utility
      • Netscape
      • Novell's TCPIP stack
      • Novell's Dialer
      • Novell's Host Presenter
      • Novell's PPP driver
    • "EUSI" (1 disk)
      • Novell's TCPIP stack
      • Novell's Host Presenter
      • Various ethernet ODI drivers
      • Custom Installer utility (allows downloading of)
        • Netscape (with helper apps)
        • WS_FTP
        • WS_FTPD
        • McGill's TN3270
        • Trumpet for Windows
  • Agreements exist with other Schools to redistribute ISC disks
    • Medical School (ISC diskettes plus their own)
    • Wharton (ISC diskettes plus their own)

Why bother?

• Reduce redundant work creating installers and strategies
• Promote campus-wide standards
• Ensure quality of products distributed and media integrity
• Minimize license and support costs
• Minimize end-user and local provider of support configuration time
• Technology needs to help people do their work, not be a hindrance (standards can help this perhaps)

Considerations for the Future: Need to explore methodology and philosophy...

• What software should we install?
• What tool(s) should we use?
• How should the installer(s) and the applications be documented?
• What kind of support should be offered to end-users or local support providers?
• Who owns the "packages"? What is the governance and who has authority? Who can use them?
• Nitty-gritty:
  • Do we need standard naming conventions?
  • What authentication method should we use?
  • What should we do about default preferences?
  • What protocols should we support?
• Additional issues:
  • Initial versus upgrade installations
  • "Boot strap" concept
  • Can this project be successful at all without "control" over desk top configurations?