Watchmen 3.1.0 System Administrator Guide
This document is a system administrator guide for the Watchmen tool. It describes how system administrator should install the application components and configure the host system.
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 is a system administrator guide for the Watchmen tool. It describes how system administrator should install the application components and configure the host system.
This document is a system administrator guide for the Watchmen tool. It describes how system administrator should install the application components and configure the host system.
This document is a system administrator guide for the Watchmen tool. It describes how system administrator should install the application components and configure the host system.
External and internal cyber-attacks pose an extreme risk to government, businesses and individuals. System attacks, resulting in compromised information are occurring more frequently and the threat to the Laboratory has never been higher. This training has been developed to help you better understand your role as a System Administrator and recognize your responsibilities within the Laboratory’s Information Security (Cyber) Program and has been revised to address newly implemented ACD 470.6 restrictions for mobile devices in secure areas.
High Performance Computing clusters and supercomputers are expensive and complex systems to manage. The software tools to manage these systems are also aging to the point where they are no longer actively developed and their methodology is antiquated. There has been a surge of new methodologies and software tools developed by the cloud providers to maximize availability of services and scalability of server deployment. The authors would like to utilize these new software tools to distribute our proof of concept, named Kraken, that will be responsible for booting and managing LANL's HPC systems in the future
Explore the source record for details and available documents.
Abstract not provided.
Explore the source record for details and available documents.
Abstract not provided.
The ANSI N43.1 Standard, currently in revision (ANSI 2007), sets forth the requirements for accelerator facilities to provide adequate protection for the workers, the public and the environment from the hazards of ionizing radiation produced during and from accelerator operations. The Standard also recommends good practices that, when followed, provide a level of radiation protection consistent with those established for the accelerator communities. The N43.1 Standard is suitable for all accelerator facilities (using electron, positron, proton, or ion particle beams) capable of producing radiation, subject to federal or state regulations. The requirements (see word 'shall') and recommended practices (see word 'should') are prescribed in a graded approach that are commensurate with the complexity and hazard levels of the accelerator facility. Chapters 4, 5 and 6 of the N43.1 Standard address specially the Radiation Safety System (RSS), both engineered and administrative systems, to mitigate and control the prompt radiation hazards from accelerator operations. The RSS includes the Access Control System (ACS) and Radiation Control System (RCS). The main requirements and recommendations of the N43.1 Standard regarding the management, technical and operational aspects of the RSS are described and condensed in this report. Clearly some aspects of the RSS policies and practices at different facilities may differ in order to meet the practical needs for field implementation. A previous report (Liu et al. 2001a), which reviews and summarizes the RSS at five North American high-energy accelerator facilities, as well as the RSS references for the 5 labs (Drozdoff 2001; Gallegos 1996; Ipe and Liu 1992; Liu 1999; Liu 2001b; Rokni 1996; TJNAF 1994; Yotam et al. 1991), can be consulted for the actual RSS implementation at various laboratories. A comprehensive report describing the RSS at the Stanford Linear Accelerator Center (SLAC 2006) can also serve as a reference.
Continuous security and configuration monitoring of information systems has been a time consuming and laborious task for system administrators at the High Performance Computing (HPC) center. Prior to this project, system administrators had to manually check the settings of thousands of nodes, which required a significant number of hours rendering the old process ineffective and inefficient. This paper explains the application of Splunk Enterprise, a software agent, and a reporting tool in the development of a user application interface to track and report on critical system updates and security compliance status of HPC Clusters. In conjunction with other configuration management systems, the reporting tool is to provide continuous situational awareness to system administrators of the compliance state of information systems. Our approach consisted of the development, testing, and deployment of an agent to collect any arbitrary information across a massively distributed computing center, and organize that information into a human-readable format. Using Splunk Enterprise, this raw data was then gathered into a central repository and indexed for search, analysis, and correlation. Following acquisition and accumulation, the reporting tool generated and presented actionable information by filtering the data according to command line parameters passed at run time. Preliminary data showed results for over six thousand nodes. Further research and expansion of this tool could lead to the development of a series of agents to gather and report critical system parameters. However, in order to make use of the flexibility and resourcefulness of the reporting tool the agent must conform to specifications set forth in this paper. This project has simplified the way system administrators gather, analyze, and report on the configuration and security state of HPC clusters, maintaining ongoing situational awareness. Rather than querying each cluster independently, compliance checking can be managed from one central location.
Large international collaborations that use decentralized computing models are becoming a custom rather than an exception in High Energy Physics. A good computing model for such big collaborations has to deal with the distribution of the experiment-specific software around the world. When the CDF experiment developed its software infrastructure, most computing was done on dedicated clusters. As a result, libraries, configuration files and large executables were deployed over a shared file system. In order to adapt its computing model to the Grid, CDF decided to distribute its software to all European Grid sites using Parrot, a user-level application capable of attaching existing programs to remote I/O systems through the filesystem interface. This choice allows CDF to use just one centralized source of code and a scalable set of caches all around Europe to efficiently distribute its code and requires almost no interaction with the existing Grid middleware or with local system administrators. This system has been in production at CDF in Europe since almost two years. Here, we present CDF implementation of Parrot and some comments on its performances.
Network Monitoring requires a substantial use of data and error analysis to overcome issues with clusters. Zenoss and Splunk help to monitor system log messages that are reporting issues about the clusters to monitoring services. Infiniband infrastructure on a number of clusters upgraded to ibmon2. ibmon2 requires different filters to report errors to system administrators. Focus for this summer is to: (1) Implement ibmon2 filters on monitoring boxes to report system errors to system administrators using Zenoss and Splunk; (2) Modify and improve scripts for monitoring and administrative usage; (3) Learn more about networks including services and maintenance for high performance computing systems; and (4) Gain a life experience working with professionals under real world situations. Filters were created to account for clusters running ibmon2 v1.0.0-1 10 Filters currently implemented for ibmon2 using Python. Filters look for threshold of port counters. Over certain counts, filters report errors to on-call system administrators and modifies grid to show local host with issue.
Rising costs of energy consumption and an ongoing effort for increases in computing performance are leading to a significant need for energy-efficient computing. Before systems such as supercomputers, servers, and datacenters can begin operating in an energy-efficient manner, the energy consumption and performance characteristics of the system must be analyzed. In this paper, we provide an analysis framework that will allow a system administrator to investigate the tradeoffs between system energy consumption and utility earned by a system (as a measure of system performance). We model these trade-offs as a bi-objective resource allocation problem. We use a popular multi-objective genetic algorithm to construct Pareto fronts to illustrate how different resource allocations can cause a system to consume significantly different amounts of energy and earn different amounts of utility. We demonstrate our analysis framework using real data collected from online benchmarks, and further provide a method to create larger data sets that exhibit similar heterogeneity characteristics to real data sets. This analysis framework can provide system administrators with insight to make intelligent scheduling decisions based on the energy and utility needs of their systems.
NodeMan is a command line tool to manage nodes in an HPC cluster. At it's core, it is an extensible framework composed of bash scripting and GNU parallel. HPC System Administrator will find it useful in that it encapsulates desired functions and allows them to be assembled in a way familiar to administrators - through pipes. In fact, NodeMan functions can work with common command line tools as long as they use stdin/stdout. System Administrators can construct moderately complex logic and filtering on a compact command line that would normally require a substantial shell script. In the spirit of clush and pdsh, it is able to run commands remotely on nodes. Additionally, NodeMan is more flexible. For example, it can interact with IPMI and naturally processes node lists for orchestrating different tools. The library of useful pre-built functions is growing. System administrators can easily create new functions and make it their own.
Distributed and parallel systems are typically managed with "static" settings: the operating system (OS) and the runtime environment (RTE) are specified at a given time and cannot be changed to fit an application's needs. This means that every time application developers want to use their application on a new execution platform, the application has to be ported to this new environment, which may be expensive in terms of application modifications and developer time. However, the science resides in the applications and not in the OS or the RTE. Therefore, it should be beneficial to adapt the OS and the RTE to the application instead of adapting the applications to the OS and the RTE. This document presents the concept of Virtual System Environments (VSE), which enables application developers to specify and create a virtual environment that properly fits their application's needs. For that four challenges have to be addressed: (i) definition of the VSE itself by the application developers, (ii) deployment of the VSE, (iii) system administration for the platform, and (iv) protection of the platform from the running VSE. We therefore present an integrated tool for the definition and deployment of VSEs on top of traditional and virtual (i.e., using system-level virtualization) execution platforms. This tool provides the capability to choose the degree of delegation for system administration tasks and the degree of protection from the application (e.g., using virtual machines). To summarize, the VSE concept enables the customization of the OS/RTE used for the execution of application by users without compromising local system administration rules and execution platform protection constraints.