SEARCH · Search NASA
Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.
Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.
This document discusses how NASA's NAS can benefit from the Sun Microsystems' Network File System (NFS). A case study is presented to demonstrate the effects of NFS on the NAS supercomputing environment. Potential problems are addressed and an implementation strategy is proposed.
The National Facility Study (NFS) was initiated in 1992 by Daniel S. Goldin, Administrator of NASA as an initiative to develop a comprehensive and integrated long-term plan for future facilities. The resulting, multi-agency NFS consisted of three Task Groups: Aeronautics, Space Operations, and Space Research and Development (R&D) Task Groups. A fourth group, the Engineering and Cost Analysis Task Group, was subsequently added to provide cross-cutting functions, such as assuring consistency in developing an inventory of space facilities. Space facilities decisions require an assessment of current and future needs. Therefore, the two task groups dealing with space developed a consistent model of future space mission programs, operations and R&D. The model is a middle ground baseline constructed for NFS analytical purposes with excursions to cover potential space program strategies. The model includes three major sectors: DOD, civilian government, and commercial space. The model spans the next 30 years because of the long lead times associated with facilities development and usage. This document, Volume 3 of the final NFS report, is organized along the following lines: Executive Summary -- provides a summary view of the 30-year mission forecast and requirements baseline, an overview of excursions from that baseline that were studied, and organization of the report; Introduction -- provides discussions of the methodology used in this analysis; Baseline Model -- provides the mission and requirements model baseline developed for Space Operations and Space R&D analyses; Excursions from the baseline -- reviews the details of variations or 'excursions' that were developed to test the future program projections captured in the baseline; and a Glossary of Acronyms.
The National Facilities Study (NFS) represents an interagency effort to develop a comprehensive and integrated long-term plan for world-class aeronautical and space facilities that meet current and projected needs for commercial and government aerospace research and development and space operations. At the request of NASA and the DOD, the National Research Council's Committee on Space Facilities has reviewed the space related findings of the NFS. The inventory of more than 2800 facilities will be an important resource, especially if it continues to be updated and maintained as the NFS report recommends. The data in the inventory provide the basis for a much better understanding of the resources available in the national facilities infrastructure, as well as extensive information on which to base rational decisions about current and future facilities needs. The working groups have used the inventory data and other information to make a set of recommendations that include estimates of cast savings and steps for implementation. While it is natural that the NFS focused on cost reduction and consolidations, such a study is most useful to future planning if it gives equal weight to guiding the direction of future facilities needed to satisfy legitimate national aspirations. Even in the context of cost reduction through facilities closures and consolidations, the study is timid about recognizing and proposing program changes and realignments of roles and missions to capture what could be significant savings and increased effectiveness. The recommendations of the Committee on Space Facilities are driven by the clear need to be more realistic and precise both in recognizing current incentives and disincentives in the aerospace industry and in forecasting future conditions for U.S. space activities.
Deceit, a distributed file system (DFS) being developed at Cornell, focuses on flexible file semantics in relation to efficiency, scalability, and reliability. Deceit servers are interchangeable and collectively provide the illusion of a single, large server machine to any clients of the Deceit service. Non-volatile replicas of each file are stored on a subset of the file servers. The user is able to set parameters on a file to achieve different levels of availability, performance, and one-copy serializability. Deceit also supports a file version control mechanism. In contrast with many recent DFS efforts, Deceit can behave like a plain Sun Network File System (NFS) server and can be used by any NFS client without modifying any client software. The current Deceit prototype uses the ISIS Distributed Programming Environment for all communication and process group management, an approach that reduces system complexity and increases system robustness.
Outlines of device support; DECnet interoperability; installation; MultiNet services; domain name server; Telnet; FTP; SMTP; DECwindows over TCP/IP; BSD r services; remote printing; RPC services and NFS server; NFS client; netcontrol; diagnostics; programming support; and MultiNet features are presented in viewgraph format.
File Servers and Supercomputing environments need high performance networks to balance the I/O requirements seen in today's demanding computing scenarios. UltraNet is one solution which permits both high aggregate transfer rates and high task-to-task transfer rates as demonstrated in actual tests. UltraNet provides this capability as both a Server-to-Server and Server-to-Client access network giving the supercomputing center the following advantages highest performance Transport Level connections (to 40 MBytes/sec effective rates); matches the throughput of the emerging high performance disk technologies, such as RAID, parallel head transfer devices and software striping; supports standard network and file system applications using SOCKET's based application program interface such as FTP, rcp, rdump, etc.; supports access to the Network File System (NFS) and LARGE aggregate bandwidth for large NFS usage; provides access to a distributed, hierarchical data server capability using DISCOS UniTree product; supports file server solutions available from multiple vendors, including Cray, Convex, Alliant, FPS, IBM, and others.
With the beginnings of the U.S. space program, there was a pressing need to develop facilities that could support the technology research and development, testing, and operations of evolving space systems. Redundancy in facilities that was once and advantage in providing flexibility and schedule accommodation is instead fast becoming a burden on scarce resources. As a result, there is a clear perception in many sectors that the U.S. has many space R&D facilities that are under-utilized and which are no longer cost-effective to maintain. At the same time, it is clear that the U.S. continues to possess many space R&D facilities which are the best -- or among the best -- in the world. In order to remain world class in key areas, careful assessment of current capabilities and planning for new facilities is needed. The National Facility Study (NFS) was initiated in 1992 to develop a comprehensive and integrated long-term plan for future aerospace facilities that meets current and projected government and commercial needs. In order to assess the nation's capability to support space research and development (R&D), a Space R&D Task Group was formed. The Task Group was co-chaired by NASA and DOD. The Task Group formed four major, technologically- and functionally- oriented working groups: Human and Machine Operations; Information and Communications; Propulsion and Power; and Materials, Structures, and Flight Dynamics. In addition to these groups, three supporting working groups were formed: Systems Engineering and Requirements; Strategy and Policy; and Costing Analysis. The Space R&D Task Group examined several hundred facilities against the template of a baseline mission and requirements model (developed in common with the Space Operations Task Group) and a set of excursions from the baseline. The model and excursions are described in Volume 3 of the NFS final report. In addition, as a part of the effort, the group examined key strategic issues associated with space R&D facilities planning for the U.S., and these are discussed in Section 4 of this volume.
Several computer programs have been developed to enable efficient administration of a large, heterogeneous, UNIX-based computing and communication network that includes a variety of computers connected to a variety of subnetworks. One program provides secure software tools for administrators to create, modify, lock, and delete accounts of specific users. This program also provides tools for users to change their UNIX passwords and log-in shells. These tools check for errors. Another program comprises a client and a server component that, together, provide a secure mechanism to create, modify, and query quota levels on a network file system (NFS) mounted by use of the VERITAS File SystemJ software. The client software resides on an internal secure computer with a secure Web interface; one can gain access to the client software from any authorized computer capable of running web-browser software. The server software resides on a UNIX computer configured with the VERITAS software system. Directories where VERITAS quotas are applied are NFS-mounted. Another program is a Web-based, client/server Internet Protocol (IP) address tool that facilitates maintenance lookup of information about IP addresses for a network of computers.
ISIS and META are two distributed systems projects at Cornell University. The ISIS project, has developed a new methodology, virtual synchrony, for writing robust distributed software. This approach is directly supported by the ISIS Toolkit, a programming system that is distributed to over 300 academic and industrial sites. Several interesting applications that exploit the strengths of ISIS, including an NFS-compatible replicated file system, are being developed. The META project, is about distributed control in a soft real time environment incorporating feedback. This domain encompasses examples as diverse as monitoring inventory and consumption on a factory floor and performing load-balancing on a distributed computing system. One of the first uses of META is for distributed application management: the tasks of configuring a distributed program, dynamically adapting to failures, and monitoring its performance. Recent progress and current plans are presented. This approach to distributed computing, a philosophy that is believed to significantly distinguish the work from that of others in the field, is explained.
The ISIS project has developed a new methodology, virtual synchony, for writing robust distributed software. High performance multicast, large scale applications, and wide area networks are the focus of interest. Several interesting applications that exploit the strengths of ISIS, including an NFS-compatible replicated file system, are being developed. The META project is distributed control in a soft real-time environment incorporating feedback. This domain encompasses examples as diverse as monitoring inventory and consumption on a factory floor, and performing load-balancing on a distributed computing system. One of the first uses of META is for distributed application management: the tasks of configuring a distributed program, dynamically adapting to failures, and monitoring its performance. Recent progress and current plans are reported.
A user oriented synthetic workload generator that simulates users' file access behavior based on real workload characterization is described. The model for this workload generator is user oriented and job specific, represents file I/O operations at the system call level, allows general distributions for the usage measures, and assumes independence in the file I/O operation stream. The workload generator consists of three parts which handle specification of distributions, creation of an initial file system, and selection and execution of file I/O operations. Experiments on SUN NFS are shown to demonstrate the usage of the workload generator.
The needs of the designer of a solid core nuclear rocket engine are discussed. Some of the topics covered include: (1) a flight thrust module/feed system module assembly; (2) a nuclear thermal rocket (NTR), expander cycle, dual T/P; (3) turbopump operating conditions; (4) typical system parameters; (5) growth capability composite fuel elements; (6) a NTR radiation cooled nozzle extension; (7) a NFS-3B Feed System; and (8) a NTR Integrated Pneumatic-Fluidics Control System.
In previous efforts, a two-dimensional full Navier-Stokes (FNS) code (SCRAM2D) was used in a design process that involved parametric modifications of the inlet geometry to arrive at what appeared to be an optimum inlet flowfield that produced a uniform flow at the exit in a very short distance. In these previous studies, the technologies for determining the contours with a 'man-in-the-loop' approach for both the ramp and cowl of the inlet were demonstrated, and nearly shock-free exiting flowfields were shown to be obtainable. The resulting two-dimensional compression contours were then used with swept sidewalls to form a three-dimensional inlet. Then the three-dimensional Navier-Stokes code (SCRAM3D) was used to investigate the inlet's three-dimensional flow. One of the major difficulties encountered in the previous studies was that associated with the relatively long time required to obtain a solution using even the 2D FNS code in the design process. Since one of the goals of high-speed inlet design is to produce inputs to the overall aircraft design in a timely manner, it was proposed for this year's research to examine 2D and 3D viscous flow solver techniques alternative to the NFS codes used to date. Areas of the inlet particularly identified for code speed up are those associated with the forebody and external flow ramp systems of the inlet. In these areas, parabolized, or space-marched, Navier-Stokes codes were proposed to be investigated for their applicability in the design process developed previously. This report describes the results of an investigation into the use of two other codes for analyzing the forebody and inlet ramp systems of high-speed inlets.
The STX mass storage system design is intended for environments requiring high speed access to large volumes of data (terabyte and greater). Prior to commitment to a product design plan, STX conducted an exhaustive study of the commercially available off-the-shelf hardware and software. STX also conducted research into the area of emerging technologies in networks and storage media so that the design could easily accommodate new interfaces and peripherals as they came on the market. All the selected system elements were brought together in a demo suite sponsored jointly by STX and ALLIANT where the system elements were evaluated based on actual operation using a client-server mirror image configuration. Testing was conducted to assess the various component overheads and results were compared against vendor data claims. The resultant system, while adequate to meet our capacity requirements, fell short of transfer speed expectations. A product team lead by STX was assembled and chartered with solving the bottleneck issues. Optimization efforts yielded a 60 percent improvement in throughput performance. The ALLIANT computer platform provided the I/O flexibility needed to accommodate a multitude of peripheral interfaces including the following: up to twelve 25MB/s VME I/O channels; up to five HiPPI I/O full duplex channels; IPI-s, SCSI, SMD, and RAID disk array support; standard networking software support for TCP/IP, NFS, and FTP; open architecture based on standard RISC processors; and V.4/POSIX-based operating system (Concentrix). All components including the software are modular in design and can be reconfigured as needs and system uses change. Users can begin with a small system and add modules as needed in the field. Most add-ons can be accomplished seamlessly without revision, recompilation or re-linking of software.
The correlator is the signal processing engine of the Very Long Baseline Array (VLBA). Radio signals are recorded on special wideband (128 Mb/s) digital recorders at the 10 telescopes, with sampling times controlled by hydrogen maser clocks. The magnetic tapes are shipped to the Array Operations Center in Socorro, New Mexico, where they are played back simultaneously into the correlator. Real-time software and firmware controls the playback drives to achieve synchronization, compute models of the wavefront delay, control the numerous modules of the correlator, and record FITS files of the fringe visibilities at the back-end of the correlator. In addition to the more than 3000 custom VLSI chips which handle the massive data flow of the signal processing, the correlator contains a total of more than 100 programmable computers, 8-, 16- and 32-bit CPUs. Code is downloaded into front-end CPU's dependent on operating mode. Low-level code is assembly language, high-level code is C running under a RT OS. We use VxWorks on Motorola MVME147 CPU's. Code development is on a complex of SPARC workstations connected to the RT CPU's by Ethernet. The overall management of the correlation process is dependent on a database management system. We use Ingres running on a Sparcstation-2. We transfer logging information from the database of the VLBA Monitor and Control System to our database using Ingres/NET. Job scripts are computed and are transferred to the real-time computers using NFS, and correlation job execution logs and status flow back by the route. Operator status and control displays use windows on workstations, interfaced to the real-time processes by network protocols. The extensive network protocol support provided by VxWorks is invaluable. The VLBA Correlator's dependence on network protocols is an example of the radical transformation of the real-time world over the past five years. Real-time is becoming more like conventional computing. Paradoxically, 'conventional' computing is also adopting practices from the real-time world: semaphores, shared memory, light-weight threads, and concurrency. This appears to be a convergence of thinking.
The Engineering Analysis and Data System (EADS) was used from April 1986 to July 1993 to support large scale scientific and engineering computation (e.g. computational fluid dynamics) at Marshall Space Flight Center. The need for an updated system resulted in a RFP in June 1991, after which a contract was awarded to Cray Grumman. EADS II was installed in February 1993, and by July 1993 most users were migrated. EADS II is a network of heterogeneous computer systems supporting scientific and engineering applications. The Common File System (CFS) is a key component of this system. The CFS provides a seamless, integrated environment to the users of EADS II including both disk and tape storage. UniTree software is used to implement this hierarchical storage management system. The performance of the CFS suffered during the early months of the production system. Several of the performance problems were traced to software bugs which have been corrected. Other problems were associated with hardware. However, the use of NFS in UniTree UCFM software limits the performance of the system. The performance issues related to the CFS have led to a need to develop a greater understanding of the CFS organization. This paper will first describe the EADS II with emphasis on the CFS. Then, a discussion of mass storage systems will be presented, and methods of measuring the performance of the Common File System will be outlined. Finally, areas for further study will be identified and conclusions will be drawn.
The principal objectives of the National Facilities Study (NFS) were to: (1) determine where U.S. facilities do not meet national aerospace needs; (2) define new facilities required to make U.S. capabilities 'world class' where such improvements are in the national interest; (3) define where consolidation and phase-out of existing facilities is appropriate; and (4) develop a long-term national plan for world-class facility acquisition and shared usage. The Space Operations Facilities Task Group defined discrete tasks to accomplish the above objectives within the scope of the study. An assessment of national space operations facilities was conducted to determine the nation's capability to meet the requirements of space operations during the next 30 years. The mission model used in the study to define facility requirements is described in Volume 3. Based on this model, the major focus of the Task Group was to identify any substantive overlap or underutilization of space operations facilities and to identify any facility shortfalls that would necessitate facility upgrades or new facilities. The focus of this initial study was directed toward facility recommendations related to consolidations, closures, enhancements, and upgrades considered necessary to efficiently and effectively support the baseline requirements model. Activities related to identifying facility needs or recommendations for enhancing U.S. international competitiveness and achieving world-class capability, where appropriate, were deferred to a subsequent study phase.
This paper will attempt to examine the industry requirements for shared network data storage and sustained high speed (10's to 100's to thousands of megabytes per second) network data serving via the NFS and FTP protocol suite. It will discuss the current structural and architectural impediments to achieving these sorts of data rates cost effectively today on many general purpose servers and will describe and architecture and resulting product family that addresses these problems. The sustained performance levels that were achieved in the lab will be shown as well as a discussion of early customer experiences utilizing both the HIPPI-IP and ATM OC3-IP network interfaces.