VMS

1
Welcome to the
VMS
LINUX
Controls Software Migration
2

• The Division has chosen to migrate the
  accelerator controls software from VMS to Linux
• The migration will take place in three phases ..
• Phase I console infrastructure
• Phase II console applications
• Phase III system services
• Acc. Controls Dept. has been working on Phase I
  for about a year and are nearing completion

3

• Phase II will be a division wide effort
• Management team ..
• Membership
• Peter Kasper (Leader)
• Wally Kissel
• Carl Schumann (Phase I leader)
• Liaisons from each affected department
• Role
• Ensure all applications get migrated on an
  appropriate schedule and receive appropriate
  testing
• The actual migration of an application will be
  the responsibility of its Keeper

4
Web Resources

• Migration home page ..
• http//www-ad.fnal.gov/controls/lcpp/
• Bookmark it!
• Contains management tools
• Lists of applications
• List of suspect keeper assignments
• And documentation
• Brief introduction to Unix

5
Short Term Strategy

• Whos doing what
• Are the keeper assignments appropriate?
• Scheduling
• In what order should the applications be
  migrated?
• Testing
• How much is needed for each application?
• We need your input to answer them
• We cant get started without answers

6
Who is Doing What and Who Cares?

• Who (Suspect Keepers) (List by Keeper)
• Some keeper assignments are no longer appropriate
• Some keepers are overloaded
• What (Obsolete Applications)
• We have identified many (probably) obsolete
  applications list needs checking
• Who Cares (List by Department)
• Department affiliation is the list of
  stakeholders for a given application
• Is our list correct?

7
Scheduling (1)

• There will be a period in which some applications
  will have been migrated to Linux and some will
  have not
• Phase I will supply us with a Duplex Console
  which will be able to launch applications on
  either platform
• In order for this to work properly we need to
  worry about the order in which applications are
  migrated

8
Scheduling (2)

• Operationally critical applications should not be
  in the first wave
• Applications that could benefit from more CPU and
  memory should migrate early
• Some applications are coupled and hence should go
  together
• PA with its SAs
• Sequencer groups
• Applications sharing files

9
Scheduling (3)

• We still need to work out the details
• Some relationships can be determined with
  software tools
• Some will be more subtle
• We are certain we will need your help in
  identifying these relationships

10
Testing

• An application is not migrated until it has been
  certified as working on Unix
• Level of testing will depend on ...
• Program complexity
• Operational sensitivity
• The keeper can handle simple applications
• But some will probably require
• Beam time for testing and debugging
• Formal sign-offs by all affiliated departments

11
Summary

• The migration is happening!
• Spread the word!
• Initially your role will be to supply us with the
  information we need and give us feedback on the
  process
• In the long run you will oversee the progress
  within your department and give us feedback on
  the process