GridFTP DSI Component Introduction Sample Clauses

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
AutoNDA by SimpleDocs
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. Figure 30: GridFTP iRODS DSI module sequence diagram 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. Thi...
Sample 1

Related to GridFTP DSI Component Introduction

  • Program Components Activities and services delivered under this Program Element align with Foundational Programs and Foundational Capabilities, as defined in Oregon’s Public Health Modernization Manual, (xxxx://xxx.xxxxxx.xxx/oha/PH/ABOUT/TASKFORCE/Documents/public_health_modernization_man ual.pdf) as well as with public health accountability outcome and process metrics (if applicable) as follows:

  • 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. OGS CENTRALIZED CONTRACT MODIFICATIONS Contract Updates will be handled as provided in Appendix C – Contract Modification Procedures.

  • Software Components At any time during the contract period of performance, the Government may require the Contractor to remedy any failure of the software to comply with the requirements of this contract. Support shall consist of correction of errors, provision of modifications, improvements, and other products the original manufacturer makes available to the Government without charge. The Government shall also be provided full documentation of changes and/or modifications to the software provided to meet the Government's requirements.

  • Xxxxxx et al Case No. 2:16-cv-10277. The Complaint, ECF No. 1, seeks declaratory and injunctive relief under the citizen-suit provision of the Safe Drinking Water Act, 42 U.S.C. § 300j-8(a);

  • Authorized User Overview and Mini-Bid Process Project Based IT Consulting Services Contracts enable Authorized Users to use a competitive Mini-bid Process to acquire Services on an as-needed basis, for qualified IT Projects. Project Based IT Consulting Services may include, but will not be limited to projects requiring: analysis, data classification, design, development, testing, quality assurance, security and associated training for Information Technology based applications. See section 1.3 Out of Scope Work for a listing of projects expressly excluded from the scope of this Contract. An Authorized User Agreement for Project Based IT Consulting Services will be governed first by the terms and conditions specified in the OGS Centralized Contract and second by terms and conditions added to the Authorized User Statement of Work. Additional terms and conditions shall not conflict with or modify the terms and conditions of the OGS Centralized Contract. NYS Executive Agencies must adhere to all internal processes and approvals including, as required, approval from NYS Office of Information Technology Services. Other Authorized Users must adhere to their own internal processes and approvals. In accordance with Appendix B, section 28, Modification of Contract Terms, an Authorized User may add additional required terms and conditions to this Mini-Bid and resultant Authorized User Agreement only if such terms and conditions (1) are more favorable to the Authorized User and (2) do not conflict with or supersede the OGS Centralized Contract terms and conditions. Examples of additional terms and conditions include: • Expedited delivery timeframe; • Additional incentives, such as discount for expedited payment/Procurement Card use; and • Any additional requirements imposed by the funding source or Federal law.

  • Unbundled Voice Loop – SL2 (UVL-SL2 Loops may be 2-wire or 4-wire circuits, shall have remote access test points, and will be designed with a DLR provided to NewPhone. SL2 circuits can be provisioned with loop start, ground start or reverse battery signaling. OC is provided as a standard feature on XX0 Xxxxx. The OC feature will allow NewPhone to coordinate the installation of the Loop with the disconnect of an existing customer’s service and/or number portability service. In these cases, BellSouth will perform the order conversion with standard order coordination at its discretion during normal work hours.

  • Unbundled Subloop Distribution (USLD) 2.8.2.1 The USLD facility is a dedicated transmission facility that BellSouth provides from an End User’s point of demarcation to a BellSouth cross-connect device. The BellSouth cross-connect device may be located within a remote terminal (RT) or a stand-alone cross-box in the field or in the equipment room of a building. The USLD media is a copper twisted pair that can be provisioned as a 2-wire or 4-wire facility. BellSouth will make available the following subloop distribution offerings where facilities exist: USLD – Voice Grade (USLD-VG) Unbundled Copper Subloop (UCSL) USLD – Intrabuilding Network Cable (USLD-INC (aka riser cable))

  • Authorized User Engagement Requirements 1. All Authorized User Agreements shall be no longer than three (3) years in duration.

  • Baseline For purposes of measuring a reduction in net tax revenue, the interim final rule measures actual changes in tax revenue relative to a revenue baseline (baseline). The baseline will be calculated as fiscal year 2019 (FY 2019) tax revenue indexed for inflation in each year of the covered period, with inflation calculated using the Bureau of Economic Analysis’s Implicit Price Deflator.163 FY 2019 was chosen as the starting year for the baseline because it is the last full fiscal year prior to the COVID– 162 See, e.g., Tax Policy Center, How do state earned income tax credits work?, https:// xxx.xxxxxxxxxxxxxxx.xxx/xxxxxxxx-xxxx/xxx-xx- state-earned-income-tax-credits-work/ (last visited May 9, 2021).

  • Purchase Order Flip via Ariba Network (AN) The online process allows suppliers to submit invoices via the AN for catalog and non- catalog goods and services. Contractors have the ability to create an invoice directly from their Inbox in their AN account by simply “flipping” the purchase order into an invoice. This option does not require any special software or technical capabilities. For the purposes of this section, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP the right and license to use, reproduce, transmit, distribute, and publicly display within the system the information outlined above. In addition, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within the system the Contractor’s trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract.

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