GridFTP DSI Component Introduction Sample Clauses

GridFTP DSI Component Introduction. The following diagram reflects the interaction process between iRODS and the GridFTP server with the iRODS DSI module. In the picture the required configuration files are included too: gridmapfile and irodsresourcemap.conf. The GridFTP DSI supports the following iRODS functionalities:  Connection to an iRODS space (reading information from .irodsEnv file)  Data-objects creation and writing (managing iRODS resources)  Data-objects checksum calculation  Collections creation  Data-objects opening and reading  Data-objects removal  Collection removal  Query to the iRODS database (ICAT)  Collections listing These functionalities are sufficient and necessary to handle all the operations made available by the main GridFTP clients, such as:  PUT: store files and folders into iRODS: ‒ single file ‒ multi files ‒ folder recursively ‒ managing iRODS resources ‒ with checksum calculation  GET: get data-objects and collections from iRODS: ‒ single file ‒ multi files ‒ folder recursively ‒ with checksum calculation  DELETE: remove data-objects and collection from iRODS: ‒ single file ‒ multi files ‒ folder recursively  LIST: list data objects and collections stored in iRODS ‒ data-objects size ‒ data-objects modification time The GridFTP DSI module is implemented using the iRODS 3.2 C API starting from a DSI stub, which can be generated directly through the Globus Toolkit. When the GridFTP server receives a request (e.g. data transfer, directory creation, files browsing, etc), it forwards it to the underneath DSI module which implements the request interacting with the iRODS instance via its API functions. The GridFTP server is kept informed about any progress and/or problems. To properly handle the connection with the iRODS instance, the DSI utilizes the variables written in the .irodsEnv file; by default the iRODS environment file is located into the home directory “~/.irods/.irodsEnv” of the user who launched the GridFTP server. If necessary, the default location can be changed to point to a different file using the irodsEnvFile environment variable. The integration of a GridFTP server with iRODS also implies some changes to the configuration of the security layer to permit the two systems to interact each other. When the GridFTP server receives a connection, the inetd process (UNIX System V) forks the process and replaces the process’s owner from root to a non-privileged user for security reasons. This approach introduces a big restriction because – for...
Sample 1
AutoNDA by SimpleDocs
GridFTP DSI Component Introduction. As reported in the previous sections, because of the requirement to have a GridFTP interface in front of iRODS to perform massive data transfers, the EUDAT project initially adopted a JAVA based GridFTP server, called Xxxxxxx. However, the last release, v.0.9.0, of this component showed significant performance degradation due to a bug in the Jargon library itself. Moreover, the behaviour of Xxxxxxx was not consistent with the event-triggering model of iRODS40. Since it was not possible to fix these bugs in the short term, we decided to extend the Globus GridFTP server to replace Xxxxxxx. In fact by using the Data Storage Interface (DSI)41 the Globus GridFTP server can be relatively easily extended.. This new module consists of C-based functions, which, through the iRODS C API, can interact with iRODS. The main operations that are supported are “get”, “put”, “delete” and “list”. The GridFTP server can load the module at start-up time through a specific command line option, and therefore no changes are required in the GridFTP server typical configuration. This simplifies software support of the module as it is decoupled from future changes in the server. From the security point of view, the authentication is based on X509 certificates (GSI authentication) and a single-sign-on mechanism has been implemented between the GridFTP server and the iRODS server. If the GridFTP server is running as a privileged user, the usual Globus security is in place and it is necessary to map the GridFTP user names into iRODS ones explicitly. Otherwise, in the case of unprivileged users, it is possible to simplify the configuration, because the iRODS server trusts that the GridFTP server is relying just on its host certificate. From the performance point of view, the transfer speed of the GridFTP server using the iRODS DSI module is a great improvement in comparison to that of Xxxxxxx (see I.2). 40 Xxxxxxx creates an empty file and then “re-opens” it to write the contents, triggering the object creation event inside iRODS twice. This event causes the execution of a certain number of rules, which should not be repeated two times for each object. 41 xxxx://xxxxxx.xxx.xx/toolkit/docs/5.2/5.2.4/gridftp/developer/#idp5046480
Sample 1

Related to GridFTP DSI Component Introduction

  • DISTRIBUTION OF CONTRACTOR PRICE LIST AND CONTRACT APPENDICES Contractor shall provide Authorized Users with electronic copies of the Contract, including price lists and Appendices, upon request. Contract Updates will be handled as provided in Appendix C – Contract Modification Procedures.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If ECI chooses to subtend a Verizon access Tandem, ECI’s NPA/NXX must be assigned by ECI to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 ECI shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from ECI’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office ECI utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow ECI’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Evaluation Software If the Software is an evaluation version or is provided to You for evaluation purposes, then, unless otherwise approved in writing by an authorized representative of Licensor, Your license to use the Software is limited solely for internal evaluation purposes in non-production use and in accordance with the terms of the evaluation offering under which You received the Software, and expires 90 days from installation (or such other period as may be indicated within the Software). Upon expiration of the evaluation period, You must discontinue use of the Software, return to an original state any actions performed by the Software, and delete the Software entirely from Your system and You may not download the Software again unless approved in writing by an authorized representative of Licensor. The Software may contain an automatic disabling mechanism that prevents its use after a certain period of time. RESTRICTIONS

  • Start-Up and Synchronization Consistent with the mutually acceptable procedures of the Developer and Connecting Transmission Owner, the Developer is responsible for the proper synchronization of the Large Generating Facility to the New York State Transmission System in accordance with NYISO and Connecting Transmission Owner procedures and requirements.

  • Laboratory Testing All laboratories selected by UPS Freight for analyzing Controlled Substances Testing will be HHS certified.

  • SHOP DRAWINGS, PRODUCT DATA AND SAMPLES 4.12.1 Shop Drawings are drawings, diagrams, schedules and other, data specially prepared for the Work by the Contractor or any Subcontractor, manufacturer, supplier or distributor to illustrate some portion of the Work. 4.12.2 Product Data are illustrations, standard schedules, performance charts, instructions, brochures, diagrams and other information furnished by the Contractor to illustrate a material, product or system for some portion of the Work. 4.12.3 Samples are physical examples which illustrate materials, equipment or workmanship and establish standards by which the Work will be judged. 4.12.4 The Contractor shall review, approve and submit, with reasonable promptness and in such sequence as to cause no delay in the Work or in the work of the State or any separate contractor, all Shop Drawings, Product Data and Samples required by the Contract Documents. 4.12.5 By approving and submitting Shop Drawings, Product Data and Samples, the Contractor represents that he / she has determined and verified all materials, field measurements, and field construction criteria related thereto, or will do so, and that he / she has checked and coordinated the information contained within such submittals with the requirements of the Work and of the Contract Documents. 4.12.6 The Contractor shall not be relieved of responsibility for any deviation from the requirements of the Contract Documents by the Architect's approval of Shop Drawings, Product Data or Samples under Subparagraph 2.2.7 of these General Conditions unless the Contractor has specifically informed the Architect and the State in writing of such deviation at the time of sub- mission and the Architect and the State has given written approval to the specific deviation. The Contractor shall not be relieved from responsibility for errors or omissions in the Shop Drawings, Product Data or Samples by the Architect's approval thereof. 4.12.7 The Contractor shall direct specific attention, in writing or on resubmitted Shop Drawings, Product Data or Samples, to revisions other than those requested by the Architect on previous submittals. 4.12.8 No portion of the Work requiring submission of a Shop Drawing, Product Data or Sample shall be commenced until the submittal has been approved by the Architect as provided in Subparagraph 2.2.7 of these General Conditions. All such portions of the Work shall be in accordance with approved submittals.

  • OPEN SOURCE COMPONENTS The DS Offerings may include open source components. Whenever notices (such as acknowledgment, copies of licenses or attribution notice) are required by the original licensor, such notices are included in the Documentation of the DS Offerings. Moreover, some open source components may not be distributed and licensed under the terms of the Agreement but under the terms of their original licenses as set forth in the Documentation of the DS Offerings themselves. Source code for open source software components is available upon request. Except for components mentioned in the section EXCLUSIONS below, the warranty and indemnification provided by DS under the Agreement apply to all open source software components and shall be provided by DS and not by the original licensor, but only for the use of the DS Offerings that is in compliance with the terms of the Agreement, and in conjunction with the DS Offerings. The original licensors of said open source software components provide them on an “as is” basis and without any liability whatsoever to Customer.

  • Programming Phase Schematic Design Phase: 2.2.1.3. Design Development Phase:

  • Computer Equipment Recycling Program If this Contract is for the purchase or lease of computer equipment, then Contractor certifies that it is in compliance with Subchapter Y, Chapter 361 of the Texas Health and Safety Code related to the Computer Equipment Recycling Program and the Texas Commission on Environmental Quality rules in 30 TAC Chapter 328.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Freedom has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Freedom. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Freedom (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Freedom, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Freedom will then have the option of paying the one-time SC rates to place the Loop.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!