1 / 6

SSS Deployment using OSCAR

June 2003, Argonne, IL SSS Face-to-face meeting. SSS Deployment using OSCAR. Brian Luethke, John Mugler, Thomas Naughton, Phil Pfeiffer & Stephen Scott.

betty
Télécharger la présentation

SSS Deployment using OSCAR

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. June 2003, Argonne, IL SSS Face-to-face meeting SSS Deployment using OSCAR Brian Luethke, John Mugler, Thomas Naughton, Phil Pfeiffer & Stephen Scott

  2. Need: A method for users to download & install the initial SSS suite offering later this summer/fall. Proposal: Leverage the OSCAR framework to package and distribute the SSS suite.

  3. OSCAR Framework • Cluster configuration & installation facility • Core: SIS, C3, ODA, Env-Switcher • OSCAR Package Facility • RPMs + meta file + scripts (optional items in italics) • Package classes: core, selected, & third-party • OSCAR Package Downloader (OPD)

  4. Capabilities • Package API • Bundle software (RPM) with a sane configuration • Scripts fire for configs outside of RPM %pre, %post • User input config using simple HTML forms method • Simple testing framework for packages • Meta data in XML, enhancements being added for improved multi-distro/release expressiveness • OSCAR Package Downloader (OPD) • CPAN-like facility for remote package acquisition • Some packages already included: LAM (BLCR coming soon), MAUI, also have an SSSLib and most of a Qbank

  5. Requirements • Follow directory structure • RPM form of software • Currently (oscar-2.2): RH 7.2/7.3, MDK 8.2 • Create tar.gz archive of pkg and make available in SSS release or an SSS OPD repository • Optional items: • Create XML meta file, e.g., config.xml • Perl scripts for additional cluster configs, e.g., post_install • Simple tests to verify pkg install • Documentation and licensing info • IA32 & IA64 forms • Include SRPMs

  6. Conclusion • Package authors must create RPMs for their SSS packages – then roll up as OSCAR Pkgs. • Users will be able to download individual packages or possibly have an oscar-sss release and install, configure for a working version.

More Related