Integration: the HPC-Cloud infrastructure Sample Clauses

Integration: the HPC-Cloud infrastructure. At this point it is clear that a seamless integration of computing infrastructures of different sizes in a cloud environment is a must. Exascale and cloud computing are not isolated technologies. Since a few years ago, and in an almost exponential reaction, almost all cloud providers are including HPC instances among their available offers (notably Amazon AWS, Microsoft Azure, Oracle Cloud Infrastructure or Google Cloud). Moreover, since very recently all of them provide tools to integrate the cloud provider's infrastructures with on-premises' data centers to create a unified environment. Based on the pyramidal scheme of Figure 1, which describes the anatomy of a supercomputer, Figure 2 pictures HPC-Cloud integration. Pyramids of different sizes (from single nodes to exascale supercomputers) are combined with a cloud orchestration, to which the user gains access through a web-based frontend. This integration combines the best of both worlds in a highly democratised fashion, making computer power accessible to the largest possible number of researchers. It is worth remarking that by facing exascale and cloud computing challenges simultaneously, CompBioMed is providing a large corpus of scientific and technology research about the deployment of simulation applications on HPC-Cloud infrastructure.
AutoNDA by SimpleDocs

Related to Integration: the HPC-Cloud infrastructure

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Infrastructure (a) The Borrower has and will maintain a sufficient infrastructure to conduct its business as presently conducted and as contemplated to be conducted following its execution of this Agreement.

  • Network Resource Interconnection Service (check if selected)

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Two-Way Interconnection Trunks 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and VarTec, VarTec shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.

  • Network Interconnection 26.1 Interconnection between the networks of different SERVICE PROVIDERs shall be as per National Standards of CCS No.7 issued from time to time by Telecom Engineering Centre (TEC) and also subject to technical feasibility and technical integrity of the Networks and shall be within the overall framework of interconnection regulations issued by the TRAI from time to time. However, if situation so arises, INTERCONNECTION with R2MF signaling may be permitted by LICENSOR.

  • One-Way Interconnection Trunks 2.3.1 Where the Parties have agreed to use One-Way Interconnection Trunks for the delivery of traffic from PCS to Verizon, PCS, at PCS’s own expense, shall:

  • Commencement of Interconnection Activities If the Developer executes the final LGIA, the ISO, Connecting Transmission Owner and the Developer shall perform their respective obligations in accordance with the terms of the LGIA, subject to modification by FERC. Upon submission of an unexecuted LGIA in accordance with Section 30.11.3, the Parties shall promptly comply with the unexecuted LGIA, subject to modification by FERC.

  • Foreign-Owned Companies in Connection with Critical Infrastructure If Texas Government Code, Section 2274.0102(a)(1) (relating to prohibition on contracts with certain foreign-owned companies in connection with critical infrastructure) is applicable to this Contract, pursuant to Government Code Section 2274.0102, Contractor certifies that neither it nor its parent company, nor any affiliate of Contractor or its parent company, is: (1) majority owned or controlled by citizens or governmental entities of China, Iran, North Korea, Russia, or any other country designated by the Governor under Government Code Section 2274.0103, or (2) headquartered in any of those countries.

  • Infrastructure Improvements The design, redevelopment and construction and completion of certain infrastructure improvements, including sewer, stormwater, electrical and water main improvements, along with other similar improvements.

Time is Money Join Law Insider Premium to draft better contracts faster.