Storage Resource Management: Concepts, Functionality, and Interface Specification

Size: px
Start display at page:

Download "Storage Resource Management: Concepts, Functionality, and Interface Specification"

Transcription

1 Storage Resource Management: Concepts, Functionality, and Interface Specification Main author: Arie Shoshani, LBNL Co-authors: Peter Kunszt, Heinz Stockinger, Kurt Stockinger, Erwin Laure (EDG-WP2) Jean-Philippe Baud,, Jens Jensen, Emil Knezo, Stefano Occhetti, Owen Synge, Olof Barring (EDG-WP5) Bryan Hess, Andy Kowalski, Chip Watson (Jefferson Lab) Don Petravick, Timur Perelmutov, Rich Wellner (Fermilab) Junmin Gu, Alex Sim (LBNL) Introduction Storage Resource Managers (SRMs) are middleware components whose function is to provide dynamic space allocation and file management on shared storage components on the Grid. They complement Compute Resource Managers in providing storage reservation and dynamic information on storage availability for data movement, and for planning and execution of Grid jobs. SRMs can be designed to provide effective sharing of files, by monitoring the activity of shared files, and making dynamic decisions on which files to replace when space is needed. In addition, SRMs perform automatic garbage collection of unused files by removing files whose lifetime has expired when space is needed. In this document we describe progress in the development and deployment of SRMs at several sites in the US and Europe, and the international coordination effort to standardize SRM interfaces as Web services. We describe the functionality of the latest SRM version (v.2.1) and its interface specification. SRM functionality Managing shared storage resources on the Grid is a necessary and complex task because of the diversity of the storage resources. Storage resources can vary in complexity: a single disk under a UNIX file system, large sets of disk caches or disk RAIDs, or mass storage systems (such as HPSS) that provide access to data on robotic tape systems. Making such resources sharable through Grid middleware technology requires that these systems are exposed through a uniform interface. Thus, requesting space from any of these systems should look the same to a client. We have shown that through international collaboration of achieving agreements on such common interfaces, various storage systems can interoperate. Most notably, SRMs have been built for several mass storage systems both in the US (HPSS at multiple sites, Enstore at Fermilab, JASMine at Jefferson Lab, MSS at NCAR) and in Europe (Castor at CERN, SE at Rutherford Lab), and shown to interoperate smoothly. Furthermore, several SRMs were built for disk systems as well, and they interoperate with SRMs for mass storage systems. This approach of standardizing on the functionality and the interfaces of SRMs is the backbone to Grid storage management [1, 2]. It allows multiple groups to implement their own SRMs and thus make the underlying storage system viewed as a Grid service. -1-

2 A practical problem of managing shared resources is that files are deposited in such systems and often not removed. This tends to clog and make storage systems ineffective. The problem is that the system administrators do not know which files can be safely removed. For this reason, SRMs have been designed to support different types of files and associate a lifetime with files that have temporary use. Accordingly, SRMs support the pinning of files for the duration of a lifetime, as well as releasing files as explicit requests. Similarly, spaces can be pinned for a lifetime, and released when not needed. The release of resources is an important mechanism to eliminate unnecessary storage occupancy for clients that belong to virtual organizations that keep track of storage usage by their members. Lifetime is a mechanism for the SRMs to reuse space that is not actively in use in case that the space is not released by the clients. Another aspect of SRM functionality came from the desire to simplify the Grid client s interaction with storage systems. For example, it is a lot simpler for an application client to request one thousand files in a single request from an SRM regardless of their location on the Grid, rather than having to get each file from it source location. SRMs have been designed to provide a service of accepting a multi-file request, queuing the requests for individual files, getting the files from the source locations (using a file transport service such as GridFTP) based on space availability, and streaming the files to the client. If files are found locally, they are pinned for use by the client. SRMs can therefore share files between clients, making storage usage more effective, and avoiding unnecessary file transfers over the Grid. Finally, SRMs are essential for dynamic planning of Grid jobs, by providing Grid job planners and executers a way to find available space, reserve space, move or deposit files into the reserved spaces, monitor the progress of requests, and recover from failures. A special case of an important Grid job, massive file replication, was achieved by developing a robust DataMover system on top of SRMs. The DataMover plans the transfer of an entire directory that can contain thousands of files and the SRMs provide access to the storage systems, queuing and streaming the file movement, and recovering from transient failures in the mass storage systems and the network. The DataMover was used successfully in production for the projects in the Particle Physics Data Grid (PPDG) and the Earth Science Grid (ESG). Types of files The concepts of permanent and temporary spaces are supported by most shared file systems. A permanent space is a space that a user controls, and only that user can put and remove files in that space. A temporary space is a shared space that is allocated to a user, but can be reclaimed by the file system. If space is reclaimed, all the files in that space are removed by the file system. The implication is that files in permanent and temporary spaces are also permanent and temporary, respectively. On the grid, the same concepts of permanent and temporary can be applied to file types, but temporary files require additional functionality. Temporary files on shared Grid spaces cannot be removed arbitrarily. Some minimal amount of time must be guaranteed by the SRM for the client to rely on. This is the reason for a lifetime of a file. This feature of a lifetime for a file is associated with each user accessing the file. That is, a lifetime is associated with a file for a user when the file is made available to the user. If -2-

3 another user requests the same file later, the file gets a fresh lifetime associated with that user. We refer to a file that is temporary in nature, but has a lifetime guarantee, as a volatile file. The concept of volatile files is very useful for sharing space, automatic garbage collection, and sharing of files on a temporary basis. Most shared disk caches on the Grid are likely to provide support only for volatile files. In contrast, a permanent file is a file associated with long-term storage that may or may not be shared by clients. Similar to file systems, permanent files can only be removed by the owner. The long-term storage can be based on any type of hardware, from a single disk to tertiary storage. For grid applications, one needs another type of a file that has properties of both permanent and volatile files. A durable file has the behavior of a volatile file in that it has a lifetime associated with it, but also the behavior of a permanent file in that when the lifetime expires the file is not automatically eligible for removal. Instead, the SRM may advise the client or an administrator that the lifetime expired or take some other action. For example, the SRM may move the file to a permanent space, release the durable space, and notify the client. A durable file type is necessary in order to provide temporary space for files generated by large simulations or experiments that need to be eventually archived. However, the archiving process is usually too slow, thus slowing down and wasting the computational resources. By storing durable files into available shared disk caches, the simulation can continue efficiently, yet it is guaranteed that the files will not be removed prematurely, and the files can be moved to the archive as a secondary task. This is a more reasonable approach for sharing temporary space, yet protecting important files. Similar to volatile files, durable files can be released by the client as soon as the files have been moved to a permanent location. Type of spaces In order to support space reservations, we found it useful to apply the concepts of permanent, durable, and volatile to spaces as well. The semantics are similar: permanent space is owned by the user and has an indefinite lifetime. Durable space is also owned by the user, but when lifetime expires there are two cases to consider. If the durable space does not contain any files, the space is released. If it contains durable files, the system claims all the unused space, and notifies the user that he has durable files whose lifetime expired. Volatile space also has a lifetime, but when it expires, all the space and the files in it can be removed by the SRM. Files of a certain type can only be stored in spaces of the same type. Reserving permanent space is obviously needed for dynamic archival storage reservation. Similarly, reserving volatile space is necessary for shared disk resources that are intended to be used on a temporary basis for files that cannot be discarded. Durable space is especially useful when a client generates a large number of files that need to be stored temporarily in some shared disk cache before being archived. The purpose of durable space is to reserve a guaranteed space on a temporary basis that cannot be removed without an explicit action by the client or the administrator. Similar to volatile space, durable space can be released by the client. In contrast to durable space, which is a space that cannot be removed without an explicit action, volatile space can be reclaimed by the SRM when space is needed. -3-

4 Interface specification The version of SRM currently implemented by many institutions, Version 1.x [3, 4], does not support explicit space reservations. Rather, it uses default space allocations. In addition, this version does not support directory definition and operations. In the fall of 2002, an extended working group was formed [5] to define the next version of SRM Version 2.x that will include this functionality. The current version, SRM 2.1 is designed to support the three file types and three space types described above. The specification is available in [6]. The functions supported in SRM Version 2.x are summarized below. They fall into five categories. Space management functions allow the client to reserve, release, and manage space types and duration. Once the space is assigned it can be referred to with a space token to put files in that space. Directory functions are similar to unix type functions, but let users put files of different types into a single directory. Thus, changing a file type (say from durable to permanent) does not change its position in the directory, only its assignment to the corresponding space type. Permission functions allow one user to assign read and write privileges to other users, or reassign files to other users. Data transfer functions are for the purpose of getting files into SRM spaces either from the client s space, or from other remote storage systems on the Grid. Data transfer functions support request for multiple files in a single function. Status functions return status of a request, or the SRM space as a whole. Space Management Functions srmreservespace srmreleasespace srmupdatespace srmcompactspace srmgetspacemetadata srmchangefilestoragetype srmgetspacetoken Directory Functions srmmkdir srmrmdir srmrm srmls srmmv Permission Functions srmsetpermission srmreassigntouser srmcheckpermission Data Transfer Functions srmpreparetoget srmpreparetoput srmcopy srmremovefiles srmreleasefiles srmputdone srmabortrequest srmabortfiles srmsuspendrequest srmresumerequest Status Functions srmstatusofgetrequest srmstatusofputrequest srmstatusofcopyrequest srmgetrequestsummary srmextendfilelifetime srmgetrequestid -4-

5 Detailed explanation of SRM functions In this section we explain some of the functions specified in [6] in detail to illustrate the main concepts and structure of the specification. Space Management Functions srmreservespace In: TUserID userid, TSpaceType typeofspace, String userspacetokendescription, TSizeInBytes sizeoftotalspacedesired, TSizeInBytes sizeofguaranteedspacedesired, TLifeTimeInSeconds lifetimeofspacetoreserve, TStorageSystemInfo storagesysteminfo Out: TSpaceType typeofreservedspace, TSizeInBytes sizeoftotalreservedspace, // best effort TSizeInBytes sizeofguaranteedreservedspace, TLifeTimeInSeconds lifetimeofreservedspace, TSpaceToken, referencehandleofreservedspace, TReturnStatus returnstatus This is the main space reservation function. We describe the parameters of this function and reasons for including them. The userid is provided as a string in non-secure SRMs, or can be extracted from a grid proxy for secure SRMs. The typeofspace wished to be reserved can be volatile, durable, or permanent. If space is granted, the SRM generates and returns a referencehandleofreservedspace. This space token is necessary to refer to the space when the client wishes to put files into that space. A client may reserve multiple spaces of the same type. The SRM is responsible for enforcing the total space limit allowed to a client. Because of the concern that clients may loose or forget the space token provided by the system, a client-specified userspacetokendescription can be provided as an input parameter. This allows the client to recover the space token by invoking the srmgetspacetoken function. The amount of space reserved can be negotiated. The client can specify sizeoftotalspacedesired and sizeofguaranteedspacedesired. The SRM returns the sizeoftotalreservedspace and the sizeofguaranteedreservedspace, which can be smaller than what was requested. sizeoftotalreservedspace is a best effort estimate, not a guarantee. A lifetimeofspacetoreserve can be specified as well. Lifetime is also negotiable; the SRM may return a lifetimeofreservedspace that is shorter than requested. If lifetime is not specified the SRM assigns a default lifetime. The storagesysteminfo is intended for systems that require additional information for their access such as a legacy mass storage system. That system may not support Grid security, and may require a login and password for its access. This is a way for the client to provide this information to the SRM so that the underlying system can be accessed on behalf of the client. -5-

6 The returnstatus is simply a statuscode and an explanation string. For example, a returnstatus maybe that the request is refused because the SRM is too full, or the user client exceeded the quota. The other functions in this category are explained next. srmreleasespace can be used to release space by providing a space token. Space is released when it is empty. If the space have files in it, one can force a the release of files with an explicit forcefilerelease parameter. The srmupdatespace can be used to request an increase a space that contains files and/or to get a new lifetime for the space. The srmcompactspace can be used to eliminate all unused space. This is important when space usage is charged for or counted against a client quota. If the space contains files, all the unused space gets released. The srmgetspacemetadata can be used to find out the details on used space, remaining unused space, and the remaining lifetime. The srmchangefilestoragetype is an important function that allows file types to be changed. For example, changing a durable file to permanent can have the effect of archiving the file. Of course, the space of the new type for the changed file has to be allocated by the SRM. Directory Functions The main issue for directory organization is whether to assign directories to spaces. At first glance, it seems natural that each space should have its own directory structure. But after considering various use cases it became clear that this choice is unnecessarily complex. For example, changing a file type will require moving it from one directory structure to another. Thus, the decision was made to have a single directory structure that can contain files of any type. The assignment of a file to a space is independent of its assignment to a directory location. Thus, a change of a file type only requires an adjustment of the size spaces used for the file. A directory structure is a virtual in that the file can be put into any physical location that the SRM chooses. This flexibility is essential to maintaining the same Grid file name when the SRM chooses to move the file from one physical location to another. URLs are used for the Grid file names, but the way they are used requires an explanation that is provided next. The URLs used for Grid file names consist of: protocol://machine_name/directory/file_name. When a file is put into an SRM, it is assigned a site URL or SURL. The protocol is simply srm. For example: srm://sleepy.lbl.gov:4000/tmp/foo-123. The file can be physically stored in another directory or even another machine. For the example above, it could be stored as dm.lbl.gov:4000/home /level1/foo-123. When a file is requested from the SRM using the SURL, the SRM returns the physical location and a transfer protocol that can be used to transfer the file by the client. For the example above, the transfer protocol could be gridftp, and thus the transfer URL or TURL is: gridftp://dm.lbl.gov:4000/home /level1/abc The TURL is used by the transfer functions as will be described in the next section. The srmmkdir, srmrmdir, srmrm, srmmv, and srmls have similar usage and semantics as in a Unix file system. But, the srmls requires further explanation. In Grid storage systems it is likely that directories contain thousands of file. Getting a listing of -6-

7 an entire directory can be too large. Thus, the srmls function has several parameter that can be used to limit the output. The function specified as follows: srmls In: TUserID userid, TSURLInfo[] path, TFileStorageType filestoragetype, boolean fulldetailedlist, boolean alllevelrecursive, int numoflevels, int offset, int count Out: TMetaDataPathDetail[] details, TReturnStatus returnstatus For a given directory location specified by path, one can request only files of type filestoragetype. If not specified, all file types are returned. The size of the output can be limited by limiting the details, by choosing the number of levels to traverse, and by specifying offset and count. Transfer Functions There are three main functions for transferring files: srmpreparetoget, srmpreparetoput, and srmcopy. srmpreparetoget is used to ask SRM for multiple files by their SURLs. The SRM can provide the files it has in its own storage, by pinning the files for the lifetime requested, or get the files from remote sites by using transfer functions. The srmpreparetoput is a multi-file request to for putting files into the SRM. The SRM allocates space for each file, and returns a TURL (path of directory location) where to put the file. The client can then issue the gridftp put command. The srmcopy is a multi-file request to copy files from one directory to another or from one site to another. This is a very powerful command that can be used to replicate entire directories between Grid sites in a single command. These three functions are asynchronous. This is because the transfer actions can take a long time, such as reading from a robotic tape system, or transferring a large file over a slow network. To explain the functionality of transfer functions in SRM, we consider the function srmpreparetoget in some detail. srmpreparetoget In: TUserID userid, TGetFileRequest[] arrayoffilerequest, string[] arrayoftransferprotocols, string userrequestdescription, TStorageSystemInfo storagesysteminfo, TLifeTimeInSeconds TotalRetryTime Out: TRequestToken requesttoken, TReturnStatus returnstatus, TGetRequestFileStatus[] arrayoffilestatus -7-

8 The parameter TGetFileRequest is defined as: typedef struct {TSURLInfo fromsurlinfo, TLifeTimeInSeconds lifetime, // pin time TFileStorageType filestoragetype, TSpaceToken spacetoken, TDirOption diroption } TGetFileRequest Thus, for each file, the file type, the requested lifetime, the file type, the space token, and the directory location can (but do not have to) be specified. If these are not specified default parameters are assigned. The parameter arrayoftransferprotocols provides a way to negotiate transfer protocols. The client can provide an ordered list of protocols it prefers to use, and the SRM chooses the highest possible ranked protocol, and return that with the TURL. For example, the ordered list can be GridFTP, ftp, http. If the SRM does not support GridFTP, but support ftp, it will use the ftp protocol in the TURL. We note that in this version we did not consider call-back or message posting capability. Thus, we provide instead a status function called srmstatusofgetrequest. The resonse to this call is the status of each file requested, such as pinned, or not available yet, etc. For the files that are pinned a TURL is provided, so the client can pull the file. When the client is done with the file it can use the srmreleasefiles to notify the SRM that it no longer needs the file, and the pin can be removed. A file that was released can then be removed by the SRM when it needs space. A request token is generated by the SRM for the purpose of finding the status of the request. The parameter userrequestdescription is a user-supplied string that can be used in case that the user looses the request token. It can be used in the srmgetrequestid function to recover the request tokens. The storagesysteminfo parameter can be specified for getting files from systems that require additional information (e.g. login and password), such as mass storage systems. This is same parameter as the one used when space is requested (explained above). The TotalRetryTime parameter is provided in order to deal with transient failure. For example, suppose that some files are requested form a mass storage system, such as HPSS. The system may be temporarily unavailable (perhaps for maintenance). Rather than giving up getting the files, or waiting excessively long time, this parameter can be used to set a limit on the total time for retries. The return from the requesttoget function is a requesttoken and arrayoffilestatus. The file status can include TURLs for all the files that the SRM can pinned immediately because they are available locally. The SRM specification also supports suspend and resume functions that are very useful for large file transfer requests, as well as abort and lifetime extension functions. The other transfer functions use similar parameters. -8-

9 Permissioin functions The srmsetpermission function is intended to support Unix like read, write and execute permissions on files and directories. The srmreassigntouser is a function that lets one user assign files to another user for a certain lifetime period. This is a convenient way of transferring responsibility between users. For example, a user may generate some files, put them in an SRM storage, and assign the files to another person for analysis. The user who generated the file can then release his/her space. The srmcheckpermission function is provided for the purpose of checking the original permission set of a file set by its owner. An SRM can use this function to check permission for a user from the source location ahead of time, thus avoiding transfer of files that the client is not permitted to get. Similarly, a client may want to find out which files he/she has permission to get. Summary Managing Storage on the Grid in a uniform fashion is essential for the success of Grid. This paper describes concepts and joint work on the desired functionality of components that manage Grid storage, called Storage Resource Managers (SRMs). An initial generation of SRMs, called SRM Version 1, was developed at multiple institutions in the US and Europe based on a common specification and shown to interoperate across a variety of storage systems, including legacy mass storage systems. This success has encouraged the design and specification of a second more powerful generation of SRMs, called SRM Version 2. This specification includes explicit space reservations, support for three types of files, lifetime management, and directory operations. Several groups have started implementation of this new version. This paper described the basic concepts and functionality of SRM Version 2.1. References [1] Storage Resource Managers: Middleware Components for Grid Storage, Arie Shoshani, Alex Sim, Junmin Gu, Nineteenth IEEE Symposium on Mass Storage Systems, 2002 [2] Storage Resource Managers: Essential Components for the Grid, Arie Shoshani, Alexander Sim, and Junmin Gu, in Grid Resource Management: State of the Art and Future Trends, Edited by Jarek Nabrzyski, Jennifer M. Schopf, Jan weglarz, Kluwer Academic Publishers, 2003 [3] SRM Joint Functional Design, Version [4] SRM joint methods specification version [5] [6] The Storage Resource Manager Interface Specification, version 2.1, Edited by Junmin Gu, Alex Sim, Arie Shoshani, available at -9-

10 -10-

Lawrence Berkeley National Laboratory Recent Work

Lawrence Berkeley National Laboratory Recent Work Lawrence Berkeley National Laboratory Recent Work Title Storage resource managers: Essential components for the grid Permalink https://escholarship.org/uc/item/3qk459bb Journal Grid Resource Management:

More information

Introduction to SRM. Riccardo Zappi 1

Introduction to SRM. Riccardo Zappi 1 Introduction to SRM Grid Storage Resource Manager Riccardo Zappi 1 1 INFN-CNAF, National Center of INFN (National Institute for Nuclear Physic) for Research and Development into the field of Information

More information

SRM. Dmitry Litvintsev. 7th international dcache workshop, May 27-29,2013. dcache Team. Dmitry Litvintsev. Wednesday, May 29, 13

SRM. Dmitry Litvintsev. 7th international dcache workshop, May 27-29,2013. dcache Team. Dmitry Litvintsev. Wednesday, May 29, 13 SRM 7th international dcache workshop, May 27-29,2013 Plan SRM, a reminder SRM parameters SRM troubleshooting 2 Reminder SRM middleware component implementing a standardized interface to a storage system

More information

Grid Data Management

Grid Data Management Grid Data Management Data Management Distributed community of users need to access and analyze large amounts of data Fusion community s International ITER project Requirement arises in both simulation

More information

Storage Resource Manager Interface Specification V2.2 Implementations Experience Report

Storage Resource Manager Interface Specification V2.2 Implementations Experience Report GFD-E.XXXX Grid Storage Resource Management https://forge.gridforum.org/projects/gsm-wg Editors: A. Sim A. Shoshani F. Donno J. Jensen 5/22/2009 Storage Resource Manager Interface Specification V2.2 Implementations

More information

Storage Resource Manager Interface Specification V2.2 Implementations Experience Report

Storage Resource Manager Interface Specification V2.2 Implementations Experience Report GFD-E.154 Grid Storage Resource Management https://forge.gridforum.org/projects/gsm-wg Editors: A. Sim A. Shoshani F. Donno J. Jensen 8/18/2009 Storage Resource Manager Interface Specification V2.2 Implementations

More information

Experiences in testing a Grid service in a production environment

Experiences in testing a Grid service in a production environment EWDC 2009 12th European Workshop on Dependable Computing Toulouse, France, 14 15 May, 2009 Experiences in testing a Grid service in a production environment Flavia Donno CERN, European Organization for

More information

Understanding StoRM: from introduction to internals

Understanding StoRM: from introduction to internals Understanding StoRM: from introduction to internals 13 November 2007 Outline Storage Resource Manager The StoRM service StoRM components and internals Deployment configuration Authorization and ACLs Conclusions.

More information

SDS: A Scalable Data Services System in Data Grid

SDS: A Scalable Data Services System in Data Grid SDS: A Scalable Data s System in Data Grid Xiaoning Peng School of Information Science & Engineering, Central South University Changsha 410083, China Department of Computer Science and Technology, Huaihua

More information

Grid Data Management in Action: Experience in Running and Supporting Data Management Services in the EU DataGrid Project

Grid Data Management in Action: Experience in Running and Supporting Data Management Services in the EU DataGrid Project Grid Data Management in Action: Experience in Running and Supporting Data Management Services in the EU DataGrid Project Heinz Stockinger, Flavia Donno, Erwin Laure, Shahzad Muzaffar, Peter Kunszt CERN,

More information

Storage Resource Manager Version 2.2: design, implementation, and testing experience

Storage Resource Manager Version 2.2: design, implementation, and testing experience Storage Resource Manager Version 2.2: design, implementation, and testing experience Flavia Donno (1) Co-authors: Lana Abadie (1),Paolo Badino (1), Jean-Philippe Baud (1), Ezio Corso (2), Shaun De Witt

More information

Introduction Data Management Jan Just Keijser Nikhef Grid Tutorial, November 2008

Introduction Data Management Jan Just Keijser Nikhef Grid Tutorial, November 2008 Introduction Data Management Jan Just Keijser Nikhef Grid Tutorial, 13-14 November 2008 Outline Introduction SRM Storage Elements in glite LCG File Catalog (LFC) Information System Grid Tutorial, 13-14

More information

glite Grid Services Overview

glite Grid Services Overview The EPIKH Project (Exchange Programme to advance e-infrastructure Know-How) glite Grid Services Overview Antonio Calanducci INFN Catania Joint GISELA/EPIKH School for Grid Site Administrators Valparaiso,

More information

Scientific data management

Scientific data management Scientific data management Storage and data management components Application database Certificate Certificate Authorised users directory Certificate Certificate Researcher Certificate Policies Information

More information

A scalable storage element and its usage in HEP

A scalable storage element and its usage in HEP AstroGrid D Meeting at MPE 14 15. November 2006 Garching dcache A scalable storage element and its usage in HEP Martin Radicke Patrick Fuhrmann Introduction to dcache 2 Project overview joint venture between

More information

THE GLOBUS PROJECT. White Paper. GridFTP. Universal Data Transfer for the Grid

THE GLOBUS PROJECT. White Paper. GridFTP. Universal Data Transfer for the Grid THE GLOBUS PROJECT White Paper GridFTP Universal Data Transfer for the Grid WHITE PAPER GridFTP Universal Data Transfer for the Grid September 5, 2000 Copyright 2000, The University of Chicago and The

More information

Adding SRM Functionality to QCDGrid. Albert Antony

Adding SRM Functionality to QCDGrid. Albert Antony Adding SRM Functionality to QCDGrid Albert Antony MSc in High Performance Computing The University of Edinburgh Year of Presentation: 2007 Abstract This dissertation discusses an attempt to add Storage

More information

Scalability and Performance Improvements in the Fermilab Mass Storage System

Scalability and Performance Improvements in the Fermilab Mass Storage System Journal of Physics: Conference Series Scalability and Performance Improvements in the Fermilab Mass Storage System To cite this article: Matt Crawford et al 2012 J. Phys.: Conf. Ser. 396 052024 View the

More information

Deliverable D8.9 - First release of DM services

Deliverable D8.9 - First release of DM services GridLab - A Grid Application Toolkit and Testbed Deliverable D8.9 - First release of DM services Author(s): Document Filename: Work package: Partner(s): Lead Partner: Config ID: Document classification:

More information

StorageGRID Webscale 11.0 Tenant Administrator Guide

StorageGRID Webscale 11.0 Tenant Administrator Guide StorageGRID Webscale 11.0 Tenant Administrator Guide January 2018 215-12403_B0 doccomments@netapp.com Table of Contents 3 Contents Administering a StorageGRID Webscale tenant account... 5 Understanding

More information

Introduction to Grid Computing

Introduction to Grid Computing Milestone 2 Include the names of the papers You only have a page be selective about what you include Be specific; summarize the authors contributions, not just what the paper is about. You might be able

More information

DISTRIBUTED FILE SYSTEMS & NFS

DISTRIBUTED FILE SYSTEMS & NFS DISTRIBUTED FILE SYSTEMS & NFS Dr. Yingwu Zhu File Service Types in Client/Server File service a specification of what the file system offers to clients File server The implementation of a file service

More information

The Earth System Grid: A Visualisation Solution. Gary Strand

The Earth System Grid: A Visualisation Solution. Gary Strand The Earth System Grid: A Visualisation Solution Gary Strand Introduction Acknowledgments PI s Ian Foster (ANL) Don Middleton (NCAR) Dean Williams (LLNL) ESG Development Team Veronika Nefedova (ANL) Ann

More information

Instruction Manual "Schaeffler FileExchange" Solution. Instruction Manual: "Schaeffler FileExchange" Solution

Instruction Manual Schaeffler FileExchange Solution. Instruction Manual: Schaeffler FileExchange Solution Instruction Manual "Schaeffler FileExchange" Solution Instruction Manual: "Schaeffler FileExchange" Solution Brief Description This instruction manual describes how you can use the Schaeffler FileExchange

More information

Access Coordination Of Tertiary Storage For High Energy Physics Applications

Access Coordination Of Tertiary Storage For High Energy Physics Applications Access Coordination Of Tertiary Storage For High Energy Physics Applications Luis M. Bernardo, Arie Shoshani, Alexander Sim, Henrik Nordberg Scientific Data Management Research Group NERSC Division Lawrence

More information

A VO-friendly, Community-based Authorization Framework

A VO-friendly, Community-based Authorization Framework A VO-friendly, Community-based Authorization Framework Part 1: Use Cases, Requirements, and Approach Ray Plante and Bruce Loftis NCSA Version 0.1 (February 11, 2005) Abstract The era of massive surveys

More information

AliEn Resource Brokers

AliEn Resource Brokers AliEn Resource Brokers Pablo Saiz University of the West of England, Frenchay Campus Coldharbour Lane, Bristol BS16 1QY, U.K. Predrag Buncic Institut für Kernphysik, August-Euler-Strasse 6, 60486 Frankfurt

More information

HEP replica management

HEP replica management Primary actor Goal in context Scope Level Stakeholders and interests Precondition Minimal guarantees Success guarantees Trigger Technology and data variations Priority Releases Response time Frequency

More information

3 Maintaining User Accounts in CCQAS 2.8

3 Maintaining User Accounts in CCQAS 2.8 3 Maintaining User Accounts in CCQAS 2.8 The maintenance of user accounts is the joint responsibility of the account holder and the CC/MSSP/CM who is responsible for managing user accounts. Over time,

More information

Outlook. File-System Interface Allocation-Methods Free Space Management

Outlook. File-System Interface Allocation-Methods Free Space Management File System Outlook File-System Interface Allocation-Methods Free Space Management 2 File System Interface File Concept File system is the most visible part of an OS Files storing related data Directory

More information

CHAPTER 3 RESOURCE MANAGEMENT

CHAPTER 3 RESOURCE MANAGEMENT CHAPTER 3 RESOURCE MANAGEMENT SUBTOPIC Understand Memory Management Understand Processor Management INTRODUCTION Memory management is the act of managing computer memory. This involves providing ways to

More information

WHITE PAPER Cloud FastPath: A Highly Secure Data Transfer Solution

WHITE PAPER Cloud FastPath: A Highly Secure Data Transfer Solution WHITE PAPER Cloud FastPath: A Highly Secure Data Transfer Solution Tervela helps companies move large volumes of sensitive data safely and securely over network distances great and small. We have been

More information

Grid data access on widely distributed worker nodes using scalla and SRM

Grid data access on widely distributed worker nodes using scalla and SRM Journal of Physics: Conference Series Grid data access on widely distributed worker nodes using scalla and SRM To cite this article: P Jakl et al 008 J. Phys.: Conf. Ser. 119 07019 View the article online

More information

1. Federation Participant Information DRAFT

1. Federation Participant Information DRAFT INCOMMON FEDERATION: PARTICIPANT OPERATIONAL PRACTICES [NOTE: This document should be considered a as MIT is still in the process of spinning up its participation in InCommon.] Participation in InCommon

More information

Transitioning NCAR MSS to HPSS

Transitioning NCAR MSS to HPSS Transitioning NCAR MSS to HPSS Oct 29, 2009 Erich Thanhardt Overview Transitioning to HPSS Explain rationale behind the move Introduce current HPSS system in house Present transition plans with timelines

More information

Andy Kowalski Ian Bird, Bryan Hess

Andy Kowalski Ian Bird, Bryan Hess Building the Mass Storage System at Jefferson Lab Andy Kowalski Ian Bird, Bryan Hess SURA/Jefferson Lab Jefferson Lab Who are we? Thomas Jefferson National Accelerator Facility SURA/DOE What do we do?

More information

Chapter 1: Introduction. Operating System Concepts 9 th Edit9on

Chapter 1: Introduction. Operating System Concepts 9 th Edit9on Chapter 1: Introduction Operating System Concepts 9 th Edit9on Silberschatz, Galvin and Gagne 2013 Chapter 1: Introduction 1. What Operating Systems Do 2. Computer-System Organization 3. Computer-System

More information

ControlPoint. Advanced Installation Guide. September 07,

ControlPoint. Advanced Installation Guide. September 07, ControlPoint Advanced Installation Guide September 07, 2017 www.metalogix.com info@metalogix.com 202.609.9100 Copyright International GmbH., 2008-2017 All rights reserved. No part or section of the contents

More information

Quick Start Guide TABLE OF CONTENTS COMMCELL ARCHITECTURE OVERVIEW COMMCELL SOFTWARE DEPLOYMENT INSTALL THE COMMSERVE SOFTWARE

Quick Start Guide TABLE OF CONTENTS COMMCELL ARCHITECTURE OVERVIEW COMMCELL SOFTWARE DEPLOYMENT INSTALL THE COMMSERVE SOFTWARE Page 1 of 35 Quick Start Guide TABLE OF CONTENTS This Quick Start Guide is designed to help you install and use a CommCell configuration to which you can later add other components. COMMCELL ARCHITECTURE

More information

INCOMMON FEDERATION: PARTICIPANT OPERATIONAL PRACTICES

INCOMMON FEDERATION: PARTICIPANT OPERATIONAL PRACTICES INCOMMON FEDERATION: PARTICIPANT OPERATIONAL PRACTICES Participation in InCommon Federation ( Federation ) enables the participant to use Shibboleth identity attribute sharing technologies to manage access

More information

Input/Output Management

Input/Output Management Chapter 11 Input/Output Management This could be the messiest aspect of an operating system. There are just too much stuff involved, it is difficult to develop a uniform and consistent theory to cover

More information

The glite File Transfer Service

The glite File Transfer Service The glite File Transfer Service Peter Kunszt Paolo Badino Ricardo Brito da Rocha James Casey Ákos Frohner Gavin McCance CERN, IT Department 1211 Geneva 23, Switzerland Abstract Transferring data reliably

More information

Files.Kennesaw.Edu. Kennesaw State University Information Technology Services. Introduces. Presented by the ITS Technology Outreach Team

Files.Kennesaw.Edu. Kennesaw State University Information Technology Services. Introduces. Presented by the ITS Technology Outreach Team Kennesaw State University Information Technology Services Introduces Files.Kennesaw.Edu Presented by the ITS Technology Outreach Team Last Updated 08/12/13 Powered by Xythos Copyright 2006, Xythos Software

More information

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Primavera Portfolio Management 9.0 What s New Copyright 1999-2011, Oracle and/or its affiliates. The Programs (which include both the software and documentation) contain proprietary information; they are

More information

INCOMMON FEDERATION: PARTICIPANT OPERATIONAL PRACTICES

INCOMMON FEDERATION: PARTICIPANT OPERATIONAL PRACTICES INCOMMON FEDERATION: PARTICIPANT OPERATIONAL PRACTICES Participation in the InCommon Federation ( Federation ) enables a federation participating organization ("Participant") to use Shibboleth identity

More information

Transaction service settings

Transaction service settings Transaction service settings Use this page to specify settings for the transaction service. The transaction service is a server runtime component that can coordinate updates to multiple resource managers

More information

Chapter 12. File Management

Chapter 12. File Management Operating System Chapter 12. File Management Lynn Choi School of Electrical Engineering Files In most applications, files are key elements For most systems except some real-time systems, files are used

More information

CMU-ITC ITC File System Goals. 12 September File System Group

CMU-ITC ITC File System Goals. 12 September File System Group CMU-ITC-83-031 ITC File System Goals 12 September 1983 File System Group Information Technology Center Carnegie-Mellon University Schenley Park Pittsburgh, PA 15213 ii ITC File System Goals CONTENTS Contents

More information

Boundary control : Access Controls: An access control mechanism processes users request for resources in three steps: Identification:

Boundary control : Access Controls: An access control mechanism processes users request for resources in three steps: Identification: Application control : Boundary control : Access Controls: These controls restrict use of computer system resources to authorized users, limit the actions authorized users can taker with these resources,

More information

IP Mobility vs. Session Mobility

IP Mobility vs. Session Mobility IP Mobility vs. Session Mobility Securing wireless communication is a formidable task, something that many companies are rapidly learning the hard way. IP level solutions become extremely cumbersome when

More information

Oracle Hospitality ecommerce Integration Cloud Service Security Guide Release 4.2 E

Oracle Hospitality ecommerce Integration Cloud Service Security Guide Release 4.2 E Oracle Hospitality ecommerce Integration Cloud Service Security Guide Release 4.2 E96343-01 May 2018 Copyright 2010, 2018, Oracle and/or its affiliates. All rights reserved. This software and related documentation

More information

Structure of Programming Languages Lecture 10

Structure of Programming Languages Lecture 10 Structure of Programming Languages Lecture 10 CS 6636 4536 Spring 2017 CS 6636 4536 Lecture 10: Classes... 1/23 Spring 2017 1 / 23 Outline 1 1. Types Type Coercion and Conversion Type Classes, Generics,

More information

User Databases. ACS Internal Database CHAPTER

User Databases. ACS Internal Database CHAPTER CHAPTER 12 The Cisco Secure Access Control Server Release 4.2, hereafter referred to as ACS, authenticates users against one of several possible databases, including its internal database. You can configure

More information

Talend Component tgoogledrive

Talend Component tgoogledrive Talend Component tgoogledrive Purpose and procedure This component manages files on a Google Drive. The component provides these capabilities: 1. Providing only the client for other tgoogledrive components

More information

30 Nov Dec Advanced School in High Performance and GRID Computing Concepts and Applications, ICTP, Trieste, Italy

30 Nov Dec Advanced School in High Performance and GRID Computing Concepts and Applications, ICTP, Trieste, Italy Advanced School in High Performance and GRID Computing Concepts and Applications, ICTP, Trieste, Italy Why the Grid? Science is becoming increasingly digital and needs to deal with increasing amounts of

More information

INTERNAL REPRESENTATION OF FILES:

INTERNAL REPRESENTATION OF FILES: INTERNAL REPRESENTATION OF FILES: Every file on a UNIX system has a unique inode. The inode contains the information necessary for a process to access a file, such as file ownership, access rights, file

More information

CS 167 Final Exam Solutions

CS 167 Final Exam Solutions CS 167 Final Exam Solutions Spring 2016 Do all questions. 1. The implementation given of thread_switch in class is as follows: void thread_switch() { thread_t NextThread, OldCurrent; } NextThread = dequeue(runqueue);

More information

CS370 Operating Systems

CS370 Operating Systems CS370 Operating Systems Colorado State University Yashwant K Malaiya Fall 2016 Lecture 2 Slides based on Text by Silberschatz, Galvin, Gagne Various sources 1 1 2 System I/O System I/O (Chap 13) Central

More information

File Services. File Services at a Glance

File Services. File Services at a Glance File Services High-performance workgroup and Internet file sharing for Mac, Windows, and Linux clients. Features Native file services for Mac, Windows, and Linux clients Comprehensive file services using

More information

Final Examination CS 111, Fall 2016 UCLA. Name:

Final Examination CS 111, Fall 2016 UCLA. Name: Final Examination CS 111, Fall 2016 UCLA Name: This is an open book, open note test. You may use electronic devices to take the test, but may not access the network during the test. You have three hours

More information

The Design and Evolution of Jefferson Lab s Jasmine Mass Storage System *

The Design and Evolution of Jefferson Lab s Jasmine Mass Storage System * The Design and Evolution of Jefferson Lab s Jasmine Mass Storage System * Bryan K. Hess Thomas Jefferson National Accelerator Facility bhess@jlab.org Michael Haddox-Schatz Thomas Jefferson National Accelerator

More information

Chapter 1: Introduction. Operating System Concepts 8th Edition,

Chapter 1: Introduction. Operating System Concepts 8th Edition, Chapter 1: Introduction, Administrivia Project 0 due Monday. Reading: 2.1 2.7. Next Time: Operating system structure. 1.2 Outline Process management. Storage management and characteristics. Miscellaneous

More information

Sage Construction Central Setup Guide (Version 18.1)

Sage Construction Central Setup Guide (Version 18.1) Sage 300 Construction and Real Estate Sage Construction Central Setup Guide (Version 18.1) Certified course curriculum Important Notice The course materials provided are the product of Sage. Please do

More information

Chapter 3: Process Concept

Chapter 3: Process Concept Chapter 3: Process Concept Chapter 3: Process Concept Process Concept Process Scheduling Operations on Processes Inter-Process Communication (IPC) Communication in Client-Server Systems Objectives 3.2

More information

Chapter 3: Process Concept

Chapter 3: Process Concept Chapter 3: Process Concept Chapter 3: Process Concept Process Concept Process Scheduling Operations on Processes Inter-Process Communication (IPC) Communication in Client-Server Systems Objectives 3.2

More information

INCOMMON FEDERATION: PARTICIPANT OPERATIONAL PRACTICES

INCOMMON FEDERATION: PARTICIPANT OPERATIONAL PRACTICES INCOMMON FEDERATION: PARTICIPANT OPERATIONAL PRACTICES Participation in InCommon Federation ( Federation ) enables the participant to use Shibboleth identity attribute sharing technologies to manage access

More information

Oracle Hospitality ecommerce Integration Cloud Service Security Guide Release 18.1 E

Oracle Hospitality ecommerce Integration Cloud Service Security Guide Release 18.1 E Oracle Hospitality ecommerce Integration Cloud Service Security Guide Release 18.1 E68585-02 May 2018 Copyright 2010, 2018, Oracle and/or its affiliates. All rights reserved. This software and related

More information

Memory Allocation. Static Allocation. Dynamic Allocation. Dynamic Storage Allocation. CS 414: Operating Systems Spring 2008

Memory Allocation. Static Allocation. Dynamic Allocation. Dynamic Storage Allocation. CS 414: Operating Systems Spring 2008 Dynamic Storage Allocation CS 44: Operating Systems Spring 2 Memory Allocation Static Allocation (fixed in size) Sometimes we create data structures that are fixed and don t need to grow or shrink. Dynamic

More information

CS 111. Operating Systems Peter Reiher

CS 111. Operating Systems Peter Reiher Operating System Principles: File Systems Operating Systems Peter Reiher Page 1 Outline File systems: Why do we need them? Why are they challenging? Basic elements of file system design Designing file

More information

Jetico Central Manager Administrator Guide

Jetico Central Manager Administrator Guide Jetico Central Manager Administrator Guide Introduction Deployment, updating and control of client software can be a time consuming and expensive task for companies and organizations because of the number

More information

Distributed File Systems. CS432: Distributed Systems Spring 2017

Distributed File Systems. CS432: Distributed Systems Spring 2017 Distributed File Systems Reading Chapter 12 (12.1-12.4) [Coulouris 11] Chapter 11 [Tanenbaum 06] Section 4.3, Modern Operating Systems, Fourth Ed., Andrew S. Tanenbaum Section 11.4, Operating Systems Concept,

More information

INCOMMON FEDERATION: PARTICIPANT OPERATIONAL PRACTICES

INCOMMON FEDERATION: PARTICIPANT OPERATIONAL PRACTICES INCOMMON FEDERATION: PARTICIPANT OPERATIONAL PRACTICES Participation in the InCommon Federation ( Federation ) enables a federation participating organization ("Participant") to use Shibboleth identity

More information

INCOMMON FEDERATION: PARTICIPANT OPERATIONAL PRACTICES

INCOMMON FEDERATION: PARTICIPANT OPERATIONAL PRACTICES INCOMMON FEDERATION: PARTICIPANT OPERATIONAL PRACTICES Participation in the InCommon Federation ( Federation ) enables a federation participating organization ("Participant") to use Shibboleth identity

More information

Process size is independent of the main memory present in the system.

Process size is independent of the main memory present in the system. Hardware control structure Two characteristics are key to paging and segmentation: 1. All memory references are logical addresses within a process which are dynamically converted into physical at run time.

More information

Managing Petabytes of data with irods. Jean-Yves Nief CC-IN2P3 France

Managing Petabytes of data with irods. Jean-Yves Nief CC-IN2P3 France Managing Petabytes of data with irods Jean-Yves Nief CC-IN2P3 France Talk overview Data management context. Some data management goals: Storage virtualization. Virtualization of the data management policy.

More information

A Simple Mass Storage System for the SRB Data Grid

A Simple Mass Storage System for the SRB Data Grid A Simple Mass Storage System for the SRB Data Grid Michael Wan, Arcot Rajasekar, Reagan Moore, Phil Andrews San Diego Supercomputer Center SDSC/UCSD/NPACI Outline Motivations for implementing a Mass Storage

More information

Chapter 18 Distributed Systems and Web Services

Chapter 18 Distributed Systems and Web Services Chapter 18 Distributed Systems and Web Services Outline 18.1 Introduction 18.2 Distributed File Systems 18.2.1 Distributed File System Concepts 18.2.2 Network File System (NFS) 18.2.3 Andrew File System

More information

Background. 20: Distributed File Systems. DFS Structure. Naming and Transparency. Naming Structures. Naming Schemes Three Main Approaches

Background. 20: Distributed File Systems. DFS Structure. Naming and Transparency. Naming Structures. Naming Schemes Three Main Approaches Background 20: Distributed File Systems Last Modified: 12/4/2002 9:26:20 PM Distributed file system (DFS) a distributed implementation of the classical time-sharing model of a file system, where multiple

More information

CS370 Operating Systems

CS370 Operating Systems CS370 Operating Systems Colorado State University Yashwant K Malaiya Spring 2018 Lecture 2 Slides based on Text by Silberschatz, Galvin, Gagne Various sources 1 1 2 What is an Operating System? What is

More information

Chapter 4. Protection in General-Purpose Operating Systems. ch. 4 1

Chapter 4. Protection in General-Purpose Operating Systems. ch. 4 1 Chapter 4 Protection in General-Purpose Operating Systems ch. 4 1 Chapter Outline 4.1 Protected Objects and Methods of Protection 4.2 Memory and Address Protection 4.3 Control of Access to General Objects

More information

INCOMMON FEDERATION: PARTICIPANT OPERATIONAL PRACTICES

INCOMMON FEDERATION: PARTICIPANT OPERATIONAL PRACTICES INCOMMON FEDERATION: PARTICIPANT OPERATIONAL PRACTICES Participation in the InCommon Federation ( Federation ) enables a federation participating organization ("Participant") to use Shibboleth identity

More information

The Grid Monitor. Usage and installation manual. Oxana Smirnova

The Grid Monitor. Usage and installation manual. Oxana Smirnova NORDUGRID NORDUGRID-MANUAL-5 2/5/2017 The Grid Monitor Usage and installation manual Oxana Smirnova Abstract The LDAP-based ARC Grid Monitor is a Web client tool for the ARC Information System, allowing

More information

Privileged Identity App Launcher and Session Recording

Privileged Identity App Launcher and Session Recording Privileged Identity App Launcher and Session Recording 2018 Bomgar Corporation. All rights reserved worldwide. BOMGAR and the BOMGAR logo are trademarks of Bomgar Corporation; other trademarks shown are

More information

StorNet: Co-Scheduling of End-to-End Bandwidth Reservation on Storage and Network Systems for High-Performance Data Transfers

StorNet: Co-Scheduling of End-to-End Bandwidth Reservation on Storage and Network Systems for High-Performance Data Transfers This paper was presented as part of the High-Speed Networks 2011 (HSN 2011) Workshop at IEEE INFOCOM 2011 1 StorNet: Co-Scheduling of End-to-End Bandwidth Reservation on Storage and Network Systems for

More information

ELEC 377 Operating Systems. Week 1 Class 2

ELEC 377 Operating Systems. Week 1 Class 2 Operating Systems Week 1 Class 2 Labs vs. Assignments The only work to turn in are the labs. In some of the handouts I refer to the labs as assignments. There are no assignments separate from the labs.

More information

and the GridKa mass storage system Jos van Wezel / GridKa

and the GridKa mass storage system Jos van Wezel / GridKa and the GridKa mass storage system / GridKa [Tape TSM] staging server 2 Introduction Grid storage and storage middleware dcache h and TSS TSS internals Conclusion and further work 3 FZK/GridKa The GridKa

More information

Deploy Enhancements from Sandboxes

Deploy Enhancements from Sandboxes Deploy Enhancements from Sandboxes Salesforce, Spring 18 @salesforcedocs Last updated: April 13, 2018 Copyright 2000 2018 salesforce.com, inc. All rights reserved. Salesforce is a registered trademark

More information

IBM Spectrum Protect HSM for Windows Version Administration Guide IBM

IBM Spectrum Protect HSM for Windows Version Administration Guide IBM IBM Spectrum Protect HSM for Windows Version 8.1.0 Administration Guide IBM IBM Spectrum Protect HSM for Windows Version 8.1.0 Administration Guide IBM Note: Before you use this information and the product

More information

PROCESS CONTROL BLOCK TWO-STATE MODEL (CONT D)

PROCESS CONTROL BLOCK TWO-STATE MODEL (CONT D) MANAGEMENT OF APPLICATION EXECUTION PROCESS CONTROL BLOCK Resources (processor, I/O devices, etc.) are made available to multiple applications The processor in particular is switched among multiple applications

More information

Grid Computing with Voyager

Grid Computing with Voyager Grid Computing with Voyager By Saikumar Dubugunta Recursion Software, Inc. September 28, 2005 TABLE OF CONTENTS Introduction... 1 Using Voyager for Grid Computing... 2 Voyager Core Components... 3 Code

More information

Chapter 2: Operating-System Structures. Operating System Concepts 8 th Edition

Chapter 2: Operating-System Structures. Operating System Concepts 8 th Edition Chapter 2: Operating-System Structures Operating System Concepts 8 th Edition Silberschatz, Galvin and Gagne 2009 Chapter 2: Operating-System Structures Different Services of Operating System. System Calls-

More information

for Credit is between September 5 and October 3 at midnight.

for Credit is between September 5 and October 3 at midnight. Fall 2017 Human Subjects Sona opens September 5, 2017 Last day to do studies is December 12 at midnight Last day to make changes/corrections is December 17 at midnight Longer BRIEF SUMMARY Prescreen INSTRUCTIONS.

More information

Too old and too worn out for the demands of the data center? It may be time to retire some of your tape cartridges.

Too old and too worn out for the demands of the data center? It may be time to retire some of your tape cartridges. Too old and too worn out for the demands of the data center? It may be time to retire some of your tape cartridges. 1233 Sherman Drive, Longmont, CO 80501-6133 303-774-6361 303-651-6371 (fax) www.mptapes.com

More information

Monitoring the Earth System Grid with MDS4

Monitoring the Earth System Grid with MDS4 Monitoring the Earth System Grid with MDS4 Ann Chervenak 1, Jennifer M. Schopf 2,3,4, Laura Pearlman 1, Mei-Hui Su 1, Shishir Bharathi 1, Luca Cinquini 5, Mike D Arcy 1, Neill Miller 2,3, David Bernholdt

More information

OAISYS Administrative Guide

OAISYS Administrative Guide OAISYS Administrative Guide Version 5 10/06/2008 OAISYS 7965 S. Priest Drive, Suite 105 Tempe, AZ 85284 (480) 496-9040 OAISYS Administrator Guide 1 Table of Contents: Table of Contents:... 2 OAISYS Administrative

More information

Chapter 17: Recovery System

Chapter 17: Recovery System Chapter 17: Recovery System! Failure Classification! Storage Structure! Recovery and Atomicity! Log-Based Recovery! Shadow Paging! Recovery With Concurrent Transactions! Buffer Management! Failure with

More information

Failure Classification. Chapter 17: Recovery System. Recovery Algorithms. Storage Structure

Failure Classification. Chapter 17: Recovery System. Recovery Algorithms. Storage Structure Chapter 17: Recovery System Failure Classification! Failure Classification! Storage Structure! Recovery and Atomicity! Log-Based Recovery! Shadow Paging! Recovery With Concurrent Transactions! Buffer Management!

More information

Grid Computing. MCSN - N. Tonellotto - Distributed Enabling Platforms

Grid Computing. MCSN - N. Tonellotto - Distributed Enabling Platforms Grid Computing 1 Resource sharing Elements of Grid Computing - Computers, data, storage, sensors, networks, - Sharing always conditional: issues of trust, policy, negotiation, payment, Coordinated problem

More information

Kaltura Admin Console Quick Start Guide

Kaltura Admin Console Quick Start Guide Kaltura Admin Console Quick Start Guide Login Publisher Management How to search and view the details of registered publishers How to access a KMC account of a registered publisher How to access a KMC

More information

USER GUIDE Time and Attendance User Administration Human Capital Management Suite

USER GUIDE Time and Attendance User Administration Human Capital Management Suite USER GUIDE Time and Attendance User Administration Human Capital Management Suite Ormed Information Systems Ltd. Version 1.2 (January 2015) What s Inside What s Inside...1 Introduction...2 Procedures...3

More information