Search NASA⌕ Search

SEARCH · Search NASA

Results for “Containerization”

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.

At least 19 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS2024

Exploring New Frontiers in Space Communications: Enhancing Delay Tolerant Networking through Cloud and Containerization

The High-rate Delay Tolerant Networking (HDTN) project at NASA Glenn Research Center has developed software that enables more flexible, reliable, and efficient space internetworking by using modern computing techniques such as cloud services, microservices, network function virtualization, software defined networking, and a distributed architecture. HDTN is built upon the Bundle Protocol and related convergence layers which have been developed to mitigate the challenges of the space networking environment including long delays, asymmetric data rates, and intermittent connectivity. The HDTN implementation employs asynchronous message processing tasks which allow for non-blocking operations as well as deployment in both centralized and distributed architectures. This paper investigates deploying HDTN in a containerized approach on the NASA Goddard’s Mission Cloud Platform using Amazon Web Services Elastic Compute Cloud (EC2). Commercial cloud computing will lower operating costs, provide flexible resource allocation, and allow for interconnectivity between multiple NASA centers as well as external partners. Containerization using Docker will enable greater portability and scalability for HDTN to be deployed into a variety of environments. We discuss possible NASA missions and use-cases such as the Laser Communications Relay Demonstration (LCRD) where the services provided by HDTN (reliable transport, high-rate message processing, and store-and-forward capabilities) will be enhanced through cloud computing and containerization. In addition, we describe the HDTN architecture and possible microservice-based networking approaches that can be obtained via HDTN’s configuration capabilities. Finally, we detail the EC2 specifications needed to achieve data rates greater than 1 Gbps to support optical communication missions such as LCRD.

Blake LaFuente↗
NASA NTRSDate not supplied

Demonstration of Rapid Development Through Containerization: OSE-SAT

Modern advancements in spacecraft technology have enabled engineers to develop radically smaller and lighter spacecraft, which has drastically reduced the cost of putting spacecraft into space. Despite these advancements and the shrinking cost to get spacecraft into space, space exploration is still prohibitively expensive. So much so that many space missions prefer to err on the side of caution than take on additional risk by trying newer, unproven technologies. This risk-averse mission design, while very reasonable from a program management point of view, significantly impacts engineers’ ability to solve newer, more complicated problems and limits scientists’ ability to develop more complex experiments that rely on newer technology. Often these new technologies remain stuck at lower technology readiness levels for many years due to the space community's reluctance to take on the additional risks of proving out unproven technology. The Distributed Spacecraft Autonomy (DSA) team at NASA Ames Research Center is developing a containerized solution to enable the rapid development of newer space technologies and accelerate their adoption into space missions. The Opportunistic Software Experiments for Spacecraft Autonomy Testbeds (OSE-SAT) is an on-orbit test bed that aims to reduce the amount of risk associated with newer, unproven space technologies by containerizing each experiment in its own isolated environment and providing a safe, robust, and controlled interface to access spacecraft host resources that is monitored in real time by thoroughly tested Trusted Container developed by DSA. This paper will describe DSA’s implementation of OSE-SAT and discuss the benefits, as well as challenges, of on-orbit containerization.

Aaron J Woodard↗
NASA NTRSDate not supplied

Space ROS TOFU: Flying Space ROS with Containerized Hybrid Trust

Space ROS is a distribution of Robot Operating System 2 (ROS2) targeting the specific requirements of flight software and spaceborne robotics while maintaining the flexibility that has made ROS indispensible for robotics research and industrial system integration. With Space ROS, a project can leverage the existing ROS2 ecosystem to reduce redundant development while tackling increasingly complex demands for on-device intelligence; however, there is no substitute for flight heritage to combat the risk-aversion common to spaceflight projects, and Space ROS has yet to fly. To break the collective-action standoff and gain valuable flight experience, the Distributed Spacecraft Autonomy (DSA) team at NASA Ames Research Center developed Opportunistic Software Experiments for Spacecraft Autonomy Testbeds (OSE-SAT) architecture, utilizing containerization to execute lower-trust software under traditionally verified heritage flight software for demonstration on-orbit. OSE-SAT leverages a hybrid-trust model where flexible, complex components like Space ROS can run without risk to the host spacecraft while providing validated feedback to a highly scrutinized, trusted core. We leverage this testbed to demonstrate Space ROS in flight, building heritage, and experience for projects with "Trust On First Use" (TOFU) requirements for flight heritage. We present a Space ROS component for OSE-SAT, lessons learned integrating Space ROS into a flight software stack, and the results of the first known use of Space ROS in orbit.

small satellites↗
NASA NTRS2012

Mars Technology Rover with Arm-Mounted Percussive Coring Tool, Microimager, and Sample-Handling Encapsulation Containerization Subsystem

A report describes the PLuto (programmable logic) Mars Technology Rover, a mid-sized FIDO (field integrated design and operations) class rover with six fully drivable and steerable cleated wheels, a rocker-bogey suspension, a pan-tilt mast with panorama and navigation stereo camera pairs, forward and rear stereo hazcam pairs, internal avionics with motor drivers and CPU, and a 5-degrees-of-freedom robotic arm. The technology rover was integrated with an arm-mounted percussive coring tool, microimager, and sample handling encapsulation containerization subsystem (SHEC). The turret of the arm contains a percussive coring drill and microimager. The SHEC sample caching system mounted to the rover body contains coring bits, sample tubes, and sample plugs. The coring activities performed in the field provide valuable data on drilling conditions for NASA tasks developing and studying coring technology. Caching of samples using the SHEC system provide insight to NASA tasks investigating techniques to store core samples in the future.

Younse, Paulo J.↗
NASA NTRS2017

Synchronous Separation, Seaming, Sealing and Sterilization (S4) using Brazing for Sample Containerization and Planetary Protection

The potential return of samples back to Earth from other planetary bodies would be based on planetary protection requirements that vary depending on the type of body [1]. Potential Mars Sample Return would require the protection of our planet from backward contamination. To fulfill this requirement, it would be necessary to implement “break the chain of contact (BTC)” process, where any material reaching Earth would have to be inside a container that is sealed with an extremely high level of confidence. In order to accomplish this, it would be necessary to contain the acquired samples and destroy any potential biological materials that may have contaminated the external surface of the container, while protecting the samples for further analysis. Using brazing, a novel synchronous separation, seaming, sealing and sterilization (S4) process for sample containerization and planetary protection has been conceived and demonstrated. A prototype double-wall container with inner and outer shells and Earth clean interstitial space was used for this demonstration. For potential Mars sample return, the double wall container would be consist of two halves and prepared on Earth. The on-orbit execution would consist of inserting the sample into one of the halves and then mating to the other half and melt the braze material to perform the S4 process. The use of brazing material that melts at temperatures higher than 500OC would assure sterilization of the exposed areas due to pyrolysis since carbon bonds are broken at this temperature. The process consists of two-steps, Step-1: the double wall container halves are fabricated and brazed on Earth; and Step-2: Assembly and brazing the samples on orbit. To prevent potential jamming during the process of mating the two halves of the double-wall container and the extraction of the brazed inner container, a double cone-within-cone approach has been conceived. The results of this study are described and discussed in this manuscript.

Bar-Cohen, Yoseph↗
NASA NTRS2022

Evaluating Network Performance of Containerized Test Framework for Distributed Space Systems

Distributed space systems are a mission architecture consisting of multiple spacecraft as a cohesive system which provide multipoint sampling, increased mission coverage, or improved sample resolution, while reducing mission risk through redundancy. To fully realize the potential of these systems, eventually scaling to hundreds or thousands of spacecraft, distributed space systems need to be operated as a single entity, which will enable a variety of novel scientific space missions. The Distributed Spacecraft Autonomy (DSA) project is a software project which aims to mature the technology needed for those systems, namely autonomous decision-making and swarm networking. The DSA project leverages a containerized swarm test framework to simulate spacecraft software, which can identify emergent behavior early in development. Container virtualization allows distributed spacecraft systems to be simulated entirely in software on a single computer, avoiding the overhead associated with conventional approaches like hardware facsimiles and virtual machines. For this approach to be effective, the simulated system behavior must not be artificially influenced by the swarm test framework itself. To address this, we present a series of benchmarks to quantify virtual network bandwidth available on a single-host computer and contextualize this against the network and application behavior of the DSA swarm test framework.

Distributed Spacecraft Autonomy↗
NASA NTRSDate not supplied

Containerized GEOS: Toward a Portable Climate Model

The NASA Goddard Earth Observing System (GEOS) is an Earth system model used for weather, climate, and other scientific applications. GEOS consists of linked components that can run in various configurations such as atmosphere-only and coupled atmosphere-ocean. Running this model on any new supercomputing system depends on operating systems, compilers, MPI stacks, and libraries being present and correctly configured. To remove that burden from users, our project explores building and running GEOS using Singularity containers – files containing all the needed software dependencies – on both NASA high-end computing systems and commercial cloud computing environments. Ultimately, the goal is for containerized GEOS to make it easier for users outside of NASA to deploy and run the model on any machine.

Matthew Thompson↗
NASA NTRS2003

Explosion Welding for Hermetic Containerization

A container designed for storing samples of hazardous material features a double wall, part of which is sacrificed during an explosion-welding process in which the container is sealed and transferred to a clean environment. The major advantage of this container sealing process is that once the samples have been sealed inside, the outer wall of what remains of the container is a clean surface that has not come into contact with the environment from which the samples were taken. Thus, there is no need to devise a decontamination process capable of mitigating all hazards that might be posed by unanticipated radioactive, chemical, and/or biological contamination of the outside of the container. The container sealing method was originally intended to be used to return samples from Mars to Earth, but it could also be used to store samples of hazardous materials, without the need to decontaminate its outer surface. The process stages are shown. In its initial double-wall form, the volume between the walls is isolated from the environment; in other words, the outer wall (which is later sacrificed) initially serves to protect the inner container from contamination. The sample is placed inside the container through an opening at one end, then the container is placed into a transfer dock/lid. The surfaces that will be welded together under the explosive have been coated with a soft metallic sacrificial layer. During the explosion, the sacrificial layer is ejected, and the container walls are welded together, creating a strong metallic seal. The inner container is released during the same event and enters the clean environment.

Dolgin, Benjamin↗
NASA NTRS2018

Synchronous Separation, Seaming, Sealing and Sterilization (S4) using Brazing for Sample Containerization and Planetary Protection

The return of samples back to Earth in future missions would require protection of our planet from the risk of bringing uncontrolled biological materials back with the samples. This protection would require “breaking the chain of contact (BTC)”, where any returned material reaching Earth for further analysis would have to be sealed inside a container with extremely high confidence. Therefore, the acquired samples would need to be contained while destroying any potential biological materials that may contaminate the external surface of the container. A novel process that could be used to contain returning samples has been developed and demonstrated in a quarter scale size. The process consists of brazing using non-contact induction heating that synchronously separates, seams, seals and sterilizes (S4) the container. The use of brazing involves melting at temperatures higher than 500°C and this level of heating assures sterilization of the exposed areas since all carbon bonds (namely, organic materials) are broken at this temperature. The mechanism consists of a double wall container with inner and outer shells having Earth-clean interior surfaces. The process consists of two-steps, Step-1: the double wall container halves are fabricated and brazed (equivalent to production on Earth); and Step-2 is the S4 process and it is the equivalent to the execution on-orbit around Mars. In a potential future mission, the double wall container would be split into two halves and prepared on Earth. The potential on-orbit execution would consist of inserting the orbiting sample (OS) container into one of the halves and then mated to the other half and brazed. The latest results of this effort will be described and discussed in this manuscript.

Salazar, Eduardo↗
NASA NTRS2021

Sample Return Containerization and Planetary Protection Using Brazing for Breaking the Chain of Contact to Mars

Planetary protection of Mars samples returned to Earth in a future NASA mission is a critical part of preventing uncontrolled biological materials being released from the samples. The planetary protection process requires addressing the potential risks and would involve “breaking the chain of contact (BTC)”, where any returned material reaching Earth for further analysis would have to be sealed inside a container with extremely high confidence. The sterilization process would require destroying any potential biological materials that may contaminate the external surface of the container. A novel process for containing the returned samples has been conceived and developed at JPL. The process consists of using induction heated brazing to synchronously sterilize, separate, seam and seal the container. In this case. the braze material is heated to the level of melting at temperatures higher than 500°C to assure sterilizing exposed areas since carbon bonds are broken above this temperature. The container that encloses the samples consists of double walls with interstitial space that is Earth-clean. The process consists of two-steps, where one was intended to be prepared on Earth and the second potentially executed on orbit around Mars. The latest results of this study that established the needed capability are described and discussed in this manuscript.

Shirajian, Nareg↗
NASA NTRSDate not supplied

An Integrated Software Architecture for Solar Cruiser Mission Design and Navigation

Solar Cruiser is a solar sailing mission, riding as a secondary payload to the Interstellar Mapping and Acceleration Probe (IMAP) mission, slated to launch in February of 2025. The Solar Cruiser vehicle will generate thrust via a complex, low-thrust solar sail. The extreme low-thrust nature of the solar sail will leave Solar Cruiser highly sensitive to external environmental effects (such as solar radiation pressure and high-order gravitational perturbations) throughout the entirety of flight. Because of this, preliminary operational optimization routines must be intricately tied to high-order predictive propagation models to ensure the greatest possible confidence in mission success. The Solar Cruiser Mission Design and Navigation (MDNav) team has designed a software tool suite, employing the latest in software containerization technology, to accomplish this task; allowing for seamless development across several users and operating systems. Combining JPL’s Monte toolkit with high-performance optimizers written by the University of Alabama, the proposed architecture allows for instant verification of optimized trajectories within the same development environment that the optimization takes place, removing the need for mission designers and navigators to switch between tools. The MDNav suite image deployment process is separated from the development and operational scripts to be used in flight, which allows for maintaining a low-footprint version control profile without unnecessary file bloating. This paper discusses the historical differences between previous iterations of the Solar Cruiser MDNav tool suite and the current iteration, planned operational interfaces of the tool with other software and subsystems, and the planned path forward in maintaining containerization services for the software throughout the lifetime of Solar Cruiser.

optimization↗
NASA NTRSDate not supplied

An Integrated Software Architecture for Solar Cruiser Mission Design and Navigation

Solar Cruiser is a solar sailing mission, riding as a secondary payload to the Interstellar Mapping and Acceleration Probe (IMAP) mission, expected to launch in February of 2025. The Solar Cruiser vehicle will generate thrust via a complex, low-thrust solar sail. The extreme low-thrust nature of the solar sail will leave Solar Cruiser highly sensitive to external environmental effects (such as solar radiation pressure and high-order gravitational perturbations) throughout the entirety of flight. Because of this, preliminary & operational optimization routines must be intricately tied to high-order predictive propagation models to ensure the greatest possible confidence in mission success. The Solar Cruiser Mission Design and Navigation (MDNav) team has designed a software tool suite, employing the latest in software containerization technology, to accomplish this task, allowing for seamless development across several users and operating systems. Combining JPL’s Monte toolkit with high-performance optimizers written by researchers at the University of Alabama, the proposed architecture allows for instant verification of optimized trajectories within the same development environment that the optimization takes place, removing the need for mission designers and navigators to switch between tools. The MDNav software suite itself is separated from the development and operational scripts to be used in flight, which allows for maintaining a low-footprint version control profile – thus avoiding unnecessary file bloating. This paper discusses the historical differences between previous iterations of the Solar Cruiser MDNav tool suite and the current iteration, planned operational interfaces of the tool with other software and subsystems, and the planned path forward in maintaining containerization services for the software throughout the lifetime of Solar Cruiser.

Containerization↗
NASA NTRSDate not supplied

An Integrated Software Architecture for Solar Cruiser Mission Design and Navigation

Solar Cruiser is a solar sailing mission, riding as a secondary payload to the Interstellar Mapping and Acceleration Probe (IMAP) mission, expected to launch in February of 2025. The Solar Cruiser vehicle will generate thrust via a complex, low-thrust solar sail. The extreme low-thrust nature of the solar sail will leave Solar Cruiser highly sensitive to external environmental effects (such as solar radiation pressure and high-order gravitational perturbations) throughout the entirety of flight. Because of this, preliminary & operational optimization routines must be intricately tied to high-order predictive propagation models to ensure the greatest possible confidence in mission success. The Solar Cruiser Mission Design and Navigation (MDNav) team has designed a software tool suite, employing the latest in software containerization technology, to accomplish this task, allowing for seamless development across several users and operating systems. Combining JPL’s Monte toolkit with University of Alabama’s high-performance optimizer, ASSET, the proposed architecture allows for instant verification of optimized trajectories within the same development environment that the optimization takes place, removing the need for mission designers and navigators to switch between tools. The MDNav software suite itself is separated from the development and operational scripts to be used in flight, which allows for maintaining a low-footprint version control profile – thus avoiding unnecessary file bloating. This paper discusses the historical differences between previous iterations of the Solar Cruiser MDNav tool suite and the current iteration, planned operational interfaces of the tool with other software and subsystems, and the planned path forward in maintaining containerization services for the software throughout the lifetime of Solar Cruiser.

solar cruiser↗
NASA NTRS2000

Category V Compliant Container for Mars Sample Return Missions

A novel containerization technique that satisfies Planetary Protection (PP) Category V requirements has been developed and demonstrated on the mock-up of the Mars Sample Return Container. The proposed approach uses explosive welding with a sacrificial layer and cut-through-the-seam techniques. The technology produces a container that is free from Martian contaminants on an atomic level. The containerization technique can be used on any celestial body that may support life. A major advantage of the proposed technology is the possibility of very fast (less than an hour) verification of both containment and cleanliness with typical metallurgical laboratory equipment. No separate biological verification is required. In addition to Category V requirements, the proposed container presents a surface that is clean from any, even nonviable organisms, and any molecular fragments of biological origin that are unique to Mars or any other celestial body other than Earth.

Containers↗
NASA NTRS1971

A nuclear powered air cushion freighter for the 1980's.

A design for a transoceanic, dry cargo-carrying freighter is suggested; its use and operation in port are discussed. With a gross weight of 4500 metric tons (5000 tons), more than 50 percent of which is cargo, it will cruise at 50 meters per second (100 knots) in waves 2.4 meters (8 ft) high. Its peripheral jet-flexible skirt air cushion concept and air thrustors will let the freighter go over waves 8 meters high at reduced velocity. Power comes from a 1280 megawatt, helium-cooled thermal reactor. It could dock at any major port in the world, but because it needs no surface contact, it could also travel inland to land-locked ports. A modular terminal design and methods of cargo transfer are suggested. The concept of cargo containerization influences both the freighter and terminal design.

Anderson, J. L.↗
NASA NTRS1973

Northwest passage: Trade route for large air cushion vehicles

A conceptual vehicle and powerplant (10,000-ton) nuclear-powered air-cushion vehicle (ACV) that could open the Northwest Passage and other Arctic passages to commercial traffic is identified. The report contains a description of the conceptual vehicle, including the powerplant and operations, an assessment of technical feasibility, estimates of capital and operating costs, and identification of eligible cargo and markets. A comparison of the nuclear ACV freighter with nuclear container ships shows that for containerized or roll-on/roll-off cargo the ACV would provide greatly reduced transit time between North Atlantic and North Pacific ports at a competitive cost.

Anderson, J. L.↗
NASA NTRS1976

Technical and Economic Assessment of Span-Distributed Loading Cargo Aircraft Concepts

A 700,000 kg (1,540,000-lb) aircraft with a cruise Mach number of 0.75 was found to be optimum for the specified mission parameters of a 272 155-kg (600,000-lb) payload, a 5560-km (3000-n.mi.) range, and an annual productivity of 113 billion revenue-ton km (67 billion revenue-ton n. mi.). The optimum 1990 technology level spanloader aircraft exhibited the minimum 15-year life-cycle costs, direct operating costs, and fuel consumption of all candidate versions. Parametric variations of wing sweep angle, thickness ratio, rows of cargo, and cargo density were investigated. The optimum aircraft had two parallel rows of 2.44 x 2.44-m (8 x 8-ft) containerized cargo with a density of 160 kg/cu m (10 lb/ft 3) carried throughout the entire 101-m (331-ft) span of the constant chord, 22-percent thick, supercritical wing. Additional containers or outsized equipment were carried in the 24.4-m (80-ft) long fuselage compartment preceding the wing. Six 284,000-N (64,000-lb) thrust engines were mounted beneath the 0.7-rad (40-deg) swept wing. Flight control was provided by a 36.6-m (120-ft) span canard surface mounted atop the forward fuselage, by rudders on the wingtip verticals and by outboard wing flaperons.

Johnston, W. M.↗