Virtual Core. A virtual core is the unit of processing power in a virtual (or otherwise emulated) hardware system. A virtual core is the virtual representation of one or more hardware threads. Virtual OSEs use one or more virtual cores.
Virtual Core Sample Clauses
Related to Virtual Core
Perth-Huron The Employer recognizes the Union as the bargaining agent of all Registered Nurses, and Nurses with a Temporary Certificate of Registration employed in a nursing capacity by the VON Canada – Ontario Branch Perth-Huron Site in the City of Stratford and at the satellite office located in Listowel, Ontario (285 Xxxxx Avenue North), save and except Supervisors and persons above the rank of Supervisor.
TO THE STANDARD CONTRACTUAL CLAUSES This Appendix forms part of the Clauses and must be completed and signed by the parties.
citizens abroad Unless the circumstances described in the parenthetical in paragraph 1 above are applicable, either (a) at the time the buy order was originated, the buyer was outside the United States or we and any person acting on our behalf reasonably believed that the buyer was outside the United States or (b) the transaction was executed in, on or through the facilities of a designated offshore securities market, and neither we nor any person acting on our behalf knows that the transaction was pre-arranged with a buyer in the United States.
Data Storage Where required by applicable law, Student Data shall be stored within the United States. Upon request of the LEA, Provider will provide a list of the locations where Student Data is stored.
Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.
Standard Contractual Clauses Where (i) Personal Data of an EEA or Swiss based Controller is processed in a country outside the EEA, Switzerland and any country, organization or territory acknowledged by the European Union as safe country with an adequate level of data protection under Art. 45 GDPR, or where (ii) Personal Data of another Controller is processed internationally and such international processing requires an adequacy means under the laws of the country of the Controller and the required adequacy means can be met by entering into Standard Contractual Clauses, then: (a) SAP and Customer enter into the Standard Contractual Clauses; (b) Customer enters into the Standard Contractual Clauses with each relevant Subprocessor as follows, either (i) Customer joins the Standard Contractual Clauses entered into by SAP or SAP SE and the Subprocessor as an independent owner of rights and obligations ("Accession Model") or, (ii) the Subprocessor (represented by SAP) enters into the Standard Contractual Clauses with Customer ("Power of Attorney Model"). The Power of Attorney Model shall apply if and when SAP has expressly confirmed that a Subprocessor is eligible for it through the Subprocessor list provided under Section 6.1(c), or a notice to Customer; and/or (c) Other Controllers whose use of the Cloud Services has been authorized by Customer under the Agreement may also enter into Standard Contractual Clauses with SAP and/or the relevant Subprocessors in the same manner as Customer in accordance with Sections 7.2
Number Resources, Rate Center Areas and Routing Points 8.1 Nothing in this Agreement shall be construed to limit or otherwise adversely affect in any manner either Party’s right to employ or to request and be assigned any Central Office Codes (“NXX”) pursuant to the Central Office Code Assignment Guidelines and any relevant FCC or Commission orders, as may be amended from time to time, or to establish, by Tariff or otherwise, Rate Center Areas and Routing Points corresponding to such NXX codes. 8.2 It shall be the responsibility of each Party to program and update its own switches and network systems pursuant to information provided in the LERG in order to recognize and route traffic to the other Party’s assigned NXX codes. Except as expressly set forth in this Agreement, neither Party shall impose any fees or charges whatsoever on the other Party for such activities. 8.3 Unless otherwise required by Commission order, the Rate Center Areas will be the same for each Party. During the term of this Agreement, Onvoy shall adopt the Rate Center Area and Rate Center Points that the Commission has approved for Frontier within the LATA and Tandem serving area. Onvoy shall assign whole NPA-NXX codes to each Rate Center Area unless otherwise ordered by the FCC, the Commission or another governmental entity of appropriate jurisdiction, or the LEC industry adopts alternative methods of utilizing NXXs. 8.4 Onvoy will also designate a Routing Point for each assigned NXX code. Onvoy shall designate one location for each Rate Center Area in which the Onvoy has established NXX code(s) as the Routing Point for the NPA-NXXs associated with that Rate Center Area, and such Routing Point shall be within the same LATA as the Rate Center Area but not necessarily within the Rate Center Area itself. Unless specified otherwise, calls to subsequent NXXs of Onvoy will be routed in the same manner as calls to Xxxxx’s initial NXXs. 8.5 Notwithstanding anything to the contrary contained herein, nothing in this Agreement is intended, and nothing in this Agreement shall be construed, to in any way constrain Onvoy’s choices regarding the size of the local calling area(s) that Onvoy may establish for its Customers, which local calling areas may be larger than, smaller than, or identical to Frontier’s local calling areas.
Zone File Access Agreement Registry Operator will enter into an agreement with any Internet user, which will allow such user to access an Internet host server or servers designated by Registry Operator and download zone file data. The agreement will be standardized, facilitated and administered by a Centralized Zone Data Access Provider, which may be ICANN or an ICANN designee (the “CZDA Provider”). Registry Operator (optionally through the CZDA Provider) will provide access to zone file data per Section 2.1.3 of this Specification and do so using the file format described in Section 2.1.4 of this Specification. Notwithstanding the foregoing, (a) the CZDA Provider may reject the request for access of any user that does not satisfy the credentialing requirements in Section 2.1.2 below; (b) Registry Operator may reject the request for access of any user that does not provide correct or legitimate credentials under Section 2.1.2 below or where Registry Operator reasonably believes will violate the terms of Section 2.1.5. below; and, (c) Registry Operator may revoke access of any user if Registry Operator has evidence to support that the user has violated the terms of Section 2.1.5 below.
XxxXxxxx Principles - Northern Ireland The provisions of San Francisco Administrative Code §12F are incorporated herein by this reference and made part of this Agreement. By signing this Agreement, Contractor confirms that Contractor has read and understood that the City urges companies doing business in Northern Ireland to resolve employment inequities and to abide by the XxxXxxxx Principles, and urges San Francisco companies to do business with corporations that abide by the XxxXxxxx Principles.
Agreement Xxx 0000 The Company shall not produce iron ore under this Agreement for transportation in any calendar year in excess of the approved production limit nor shall the total number of the mine workforce exceed the approved mine workforce without the prior consent in principle of the Minister and, subject to that consent, approval of detailed proposals in regard thereto in accordance with this Clause.
