SSS Deployment using OSCAR

1
SSS Deployment using OSCAR
January 2004, Argonne, IL

SSS Face-to-face meeting

• John Mugler, Thomas Naughton, Phil Pfeiffer
  Stephen Scott

2
OSCAR Cluster Toolkit

• Framework for cluster management
• simplifies installation, configuration and
  operation
• reduces time/learning curve for cluster build
• requires pre-installed headnode w. supported
  Linux distribution
• thereafter wizard guides user thru setup/install
  of entire cluster
• Package-based framework
• Content Software Configuration, Tests, Docs
• Types
• Core SIS, C3, Switcher, ODA, OPD, (Support
  Libs)
• Non-core selected third-party
• Access repositories accessible via OPD/OPDer

3
OSCAR Wizard
OSCAR-2.3 release
4
Using OSCAR for SSS

• Problem Helping users obtain and install SSS
  software.
• Solution Leverage OSCAR framework to package and
  distribute the SSS suite, sss-oscar.
• sss-oscar ? A release of OSCAR containing all
  SSS software in single downloadable bundle.

5
SSS-OSCAR TODO

• Roll SSS components into OSCAR packages
• RPM version of software
• Meta file configuration scripts
• ? See OSCAR Package HOWTO
• Create repository for OSCAR package uploads
• sss-oscar.sf.net setup to house packages
• SF.net License Other OSD-compliant Open
  Source
• Accounts CVS permissions
• Establish supported Linux distribution
• We decided upon RedHat 9.0 and standard Fast
  Ethernet

6
Good

• Packaging
• RPMs created for all SSS components!
• OSCAR packaging (varying levels)
• SourceForge project
• Central CVS location for current components
  docs
• Tracker/Emails seemed helpful folks were
  responsive
• General
• Licensing issues ironed out
• Exposed some issues with components
  interactions
• e.g., startup order, can you X-Y-Z mix of the
  components
• Integration spurred communication

7
Bad Ugly

• Packaging
• Not all init scripts are created equal (see
  HOWTO)
• Many are new to OSCAR so testing was thin
• SourceForge project
• Some pain getting SF.net accounts initially
• CVS administration (chmod my filerequest to
  SF.net)
• General
• Time constraints forced some script hacks
• Hard coding ports and greping config files
• Removed Accounting components (rebuild MAUI)
• OSCAR issues
• Testing framework too static
• Using alt. batch scheduler raised problems

8
Current Status

• Tarball available
• Fairly toxic, requires some manual interaction
• Builds full working cluster w/ subset of current
  SSS pkgs
• Updated OSCAR Pkg HOWTO
• Use /opt Switcher if possible
• Init scripts compatible with service command
• Init scripts honor start, stop, restart, (status)
• Generate config files from script not RPM
• Documentation
• Started a component config doc for
  integrators/SysAdmins

9
TODO

• Cleanup some hacks in current packaging
• Integrate remaining SSS components
• Add SSS interface to OSCAR itself (CLI)
• Need some OSCAR enhancements
• Test framework
• Scheduler abstraction
• Improve ordering for pkg startup/testing

10
Future Releases

• Establish a rough release schedule
• Setup Distributed Integration Party (DIP) Days
• Timeline/Milestones group discussion
• Coordinate with other WG schedules?
• SC03/Jan04 first alpha very rough, incomplete
  SSS pkg set
• Cleanup current release
• Integrate remaining SSS pkgs
• Integrate new OSCAR testing framework (enforce
  ordering)
• Add other OSCAR enhancements, e.g., alt. batch
  systems
• More stable SSS components/packaging
• SSS interface to OSCAR (long anticipated BCWG
  stuffo ?)
• SC04 Fully tested release with all SSS
  components

11
Resources

• Developer CVS repository
• Hosted at http//sss-oscar.sf.net
• Account requests torc_at_msr.csm.ornl.gov
• sss-oscar-0.1a2
• OSCAR Package HOWTO
• http//www.csm.ornl.gov/naughton/sss-oscar/
• Or http//sss-oscar.sf.net
• OSCAR Homepage
• http//oscar.sf.net