From: wdc@MIT.EDU
Subject: Notes: 5 January 2009 Linux / Athena support meeting
Date: January 5, 2009 12:10:49 PM EST
To: linux-ponder@mit.edu

Next meeting: 
Some time to be determined before:
11:00 AM Monday, February 2, 2009 N42-202  (Note room change)

Agenda: 

	1. Define use cases for Classes of service.

Notes from 5 January:

Agenda:
        1. More in-depth discussion of the Key Features/Services.
        2. How to pick the right meeting so most of the right people
attend.

Present: bowser, alexp, jmhunt, othomas, gettes, wdc, blang, aurora

Key Components:

A. Network
B. Kerberos/Certificates
C. Printing
D. 3rd Party Software
E. Email/Calendaring
F. Instant Messaging
G. Web Browser
H. Security/Software Update
I. VPN
J. Backup
K. Filesystem/AFS
L. Remote access configuration: Athena 10 proposes to eliminate this.

* denotes High priority service

Class of Service

Athena Cluster: ABCDEFGHK (All but JL)

Individually owned:
	Desktop Workstation on Campus: ABCDEFGHKL  (All but I)
	Off-Campus/Laptop: All A-L

Servers: ABHJKL


----

What do we mean by "Third Party Software Support"?

	Institutional supplied mechanism for MIT users to install and maintain
software from third parties.

	Institutional acquisition of software to license it, and make it
available to MIT users at low or zero cost.  May involve institutionally
provided License servers, media, or local download and/or update
facilities.

	Institutional efforts to make software more easily usable by MIT users.

----

Support Issues:

Mobility
Hardware Compatibility
Bandwidth -- Network
VMware
"Supported Platforms as VMs"
Component viability affects Distribution Supportability
Distribution Viability
Prior Community Commitment

  • No labels