Versions Compared

Old Version 2

changes.mady.by.user William D Cattey

Saved on

compared with

New Version 3

changes.mady.by.user William D Cattey

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated with info exchanged with Othomas, and then refined by Athena Release Team.

...

Over the summer of FY08 the Athena General Use Cluster footprint 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.

End of Life is targeted for July 1 2009.

Areas of exposure:

  1. Student use of Suns in Athena Clusters (small.

...

  1. )
  2. General use Solaris-only software:
  • ArcInfo: (geographic information system) – now available in the Win.MIT.edu clusters.
  • FrameMaker – This will no longer be available. Migrate documents to OpenOffice and Microsoft Office.
  • Acrobat distiller – This will no longer be available. Use word processor's built-in PDF output configuration.
  1. Faculty who don't want to give up their Suns.
  2. Classes teaching with Sun-Unique courseware.

Plan of action:

  1. Create Desktop Athena Solaris EOL Details web site with Timeline, Rationale and What to do.
  2. Meet with OEIT or ACCORD to announce this is coming and get them ready.
  3. Send out an announcement with summary Rationale, July 1 date, and summary activities: Migrate migrate migrate, and a pointer to the web site.
  4. Establish MOTD messages to warn customers of Software/Hardware End of Life.
  5. Display signs on machines in clusters warning

Customer options:

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

Deliverables / Activities

...

  1. of Software/Hardware End of Life.

...

  1. 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: wdsouza, alexp, wdc, amb.
  2. 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.
  3. Make a list of the courses with Solaris-only exposure, and identify what to do.
  4. Create a solaris-sunset email list with members: othomas, wdc, jdreed, jmhunt, gettes, bowser and an OEIT representative to receive calls for help.
  5. Quietly keep the 8 Solaris systems in 38-332 through the Fall term for classes that fall through the cracks.

Key Customers

TBA

Key Software

...