Versions Compared

Old Version 1

changes.mady.by.user William D Cattey

Saved on

compared with

New Version Current

changes.mady.by.user Oliver Thomas

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Corrected links that should have been relative instead of absolute.
Note

This is a skeletal project plan that has NOT YET been reviewed or approved for action.

Overview

For some time the Desktop Athena SPARC/Solaris configuration from Sun Microsystemshas been under review. It has reached the point where the added costs of maintaining a second Athena desktop configuration are no longer justified by the incremental value add of the desktop Athena Solaris platformof having Solaris as a second Athena desktop.

Over the summer of FY08 2008 the Athena General Use Cluster footprint number of Sun Solaris systems will fall fell to about 5044. Through FY09 outreach will be made to customers to assist appropriately in dealing with the end of life of the Athena Desktop Solaris platform.

Customer options:

  • Migrate to Linux Athena
  • Retain Solaris Hardware on an "go-it-alone" basis.

Deliverables / Activities

  • Review the Solaris-unique software offerings.
  • Establish start-up messages to warn customers of Software/Hardware End of Life.
  • Identify remaining key customers with significant Athena Solaris footprint.
  • Contact key Athena Solaris customers and assist with Migration or go-it-alone strategy.
  • Large scale email/paper mail notification of Desktop Athena Solaris end of life.

Key Customers

TBA

Key Software

...

Status

  • Goal: Begin last round of community communications by May 14, 2009
  • End of Life 1 is targeted for July 1 2009

__
1) "End of Life" in this context means almost all public student lab/cluster Solaris Athena machines are pulled and replaced with Linux Athena systems; all centrally DLC purchased Solaris Athena machines are either handed over to the DLC for local support and transition to vendor Solaris, replaced with Linux Athena systems, or decommissioned

Areas of exposure

  • Student use of Suns in Athena Clusters
    Scale=small; Impact=low
  • Faculty who don't want to give up their Suns
    Sscale=small; Impact=medium
  • Classes teaching with Sun-unique courseware
    Scale=small; Impact=high
  • General use Solaris-only software:
    • ArcInfo (GIS)
      Out of date on Athena; available for personal Windows systems and on IS&T and DUSP WIN.MIT.EDU machines
    • FrameMaker
      Will no longer be available; documents will need to be migrated to OpenOffice and Microsoft Office
    • Acrobat Distiller
      Will no longer be available; PDFs can be generated using OpenOffice built-in PDF output configuration

Additionally, we need to account for the impact on servers built from Athena Solaris. We need to identify the count of Solaris servers in the field and determine if migration or continuing to do security updates is the best approach. Note that the cost of Solaris support still drops even if only the desktop applications and services are discontinued initially, and if OS security updates are continued for a little while.

Solaris EOL Customer Options:

  1. Switch to Linux Athena hardware
  2. Migrate to work-alike software
  3. Go it alone and work directly with Sun for support

Plan of action

  1. Create Desktop Athena Solaris EOL Details web site telling users the timeline, rationale and what to do
  2. Create public Solaris Athena EOL letter for the remaining Solaris Athena community
  3. Directly deliver letter to known deliberate users
  4. Socialize EOL date for cluster Solaris Athena with OEIT, ACCORD, and other key stakeholders
  5. Establish MOTD messages to warn customers of Solaris Athena End of Life
  6. Display signs on machines in clusters warning of Solaris Athena End of Life
  7. Obtain list of faculty with Suns on their desks and get Hotline to begin migrating them ASAP. Let them forward problem customers to appropriate folks internally: othomas on point, alexp, amb, wdsouza for specific issues and resolutions
  8. Utilize mailing lists and beginning-of-term coordinated events to contact TAs and identify as many at-risk courses and course lockers as we can
  9. Make a list of the courses with Solaris-only exposure, and identify what to do
  10. Create a Solaris-sunset email list with members: othomas, jdreed, jmhunt, gettes, bowser and an OEIT representative to receive calls for help
  11. Quietly keep the 8 Solaris systems in 38-332 through the Fall term for classes that fall through the cracks
  12. Quietly keep Solaris dialups and x.dialup through Fall term for classes that fall through the cracks