Units of Measure and Purchasing Requirements Sample Clauses

Units of Measure and Purchasing Requirements. You must purchase the appropriate number and type of Red Hat Management Subscriptions based on the Unit and Supported Use Cases described in Table 1 below.
Sample 1Sample 2See All (4)
AutoNDA by SimpleDocs
Units of Measure and Purchasing Requirements. Table 2 sets forth the Unit of measure and Supported Use Cases for Red Hat Ansible Automation Platform Subscriptions. You must purchase the appropriate number and type of these Subscriptions based on the Unit and other parameters described in Table 2 below.
Sample 1
Units of Measure and Purchasing Requirements. Table 2 sets forth the Unit of measure, stacking capabilities and Supported Use Cases for various Red Hat Management Subscriptions. You must purchase the appropriate number and type of these Subscriptions based on the Unit and other parameters described in Table 2. For Virtual Nodes managed by CloudForms in a CloudForms enabled public cloud, you need to purchase Units equal to either (at your option), (a) the actual number of Units or (b) the average daily maximum Virtual Nodes managed by CloudForms in the previous 365 days. If 365 days of usage history is not available, you may use the average usage history period that is available. If managing Virtual Nodes on a public cloud, you must confirm that a specific public cloud is Red Hat CloudForms enabled.
Sample 1
Units of Measure and Purchasing Requirements. Table 3 sets forth the Unit of measure and Supported Use Cases for Red Hat Ansible Engine and Red
Sample 1
Units of Measure and Purchasing Requirements. Table 2 sets forth the Unit of measure, stacking capabilities and Supported Use Cases for various Red Hat Management Subscriptions. You must purchase the appropriate number and type of these Subscriptions based on the Unit and other parameters described in Table 2. For Virtual Nodes managed by CloudForms in a CloudForms enabled public cloud, you need to purchase Units equal to either (at your option), (a) the Table 2 Software Subscription Unit of Measure Capacity Stackable Use Case
Sample 1
Units of Measure and Purchasing Requirements. Table 3 sets forth the Unit of measure and Supported Use Cases for Red Hat Ansible Engine and Red Hat Ansible Tower Software. You must purchase the appropriate number and type of these Subscriptions based on the Unit and other parameters described in Table 3 below.
Sample 1

Related to Units of Measure and Purchasing Requirements

  • Entitlements and Purchasing Requirements You must purchase the appropriate number of Software Subscription(s), based on the number of Socket-pairs for all Managed Nodes being managed by the Red Hat CloudForms Software. A “Socket-pair” is up to two sockets each occupied by a CPU on a Managed Node. Red Hat CloudForms Software is configured to manage virtual machines on certain public clouds (a “Red Hat CloudForms Enabled Cloud”). You must purchase the appropriate number of Red Hat CloudForms for Public Cloud Software Subscriptions based on the number of Managed VMs instantiated on a Red Hat CloudForms Enabled Cloud. Please confirm that a specific public cloud is a Red Hat CloudForms Enabled Cloud prior to purchasing. A Red Hat Enterprise Linux Software Subscription is bundled with the Red Hat CloudForms Software Subscription and the fees for the Red Hat CloudForms Subscription are based on such bundled use. Any use of the Red Hat Enterprise Linux other than to run the Red Hat CloudForms Software is subject to Red Hat’s standard Software Subscription fees for such use.

  • Staffing Requirements Licensee will be in full compliance with the main studio staff requirements as specified by the FCC.

  • Surviving Requirements The termination of this contract and payment of an amount in settlement as prescribed above shall extinguish the rights, duties, and obligations of the State and the Engineer under this contract, except for those provisions that establish responsibilities that extend beyond the contract period.

  • Vesting Requirements The vesting of this Award (other than pursuant to accelerated vesting in certain circumstances as provided in Section 3 below or vesting pursuant to Section 6 below) shall be subject to the satisfaction of the conditions set forth in each of subsections A and B, as applicable, and, in each case, subsection C of this Section 2:

  • Requirements Pertaining Only to Federal Grants and Subrecipient Agreements If this Agreement is a grant that is funded in whole or in part by Federal funds:

  • Licensing Requirements (a) Employer and Employee hereby covenant and agree that this Agreement and/or Employee’s employment may be subject to the approval of one or more gaming regulatory authorities (the “Authorities”) pursuant to the provisions of the relevant gaming regulatory statutes (the “Gaming Acts”) and the regulations promulgated thereunder (the “Gaming Regulations”). Employer and Employee hereby covenant and agree to use their best efforts to obtain any and all approvals required by the Gaming Acts and/or Gaming Regulations. In the event that (i) an approval of this Agreement or Employee’s employment by the Authorities is required for Employee to carry out Employee’s duties and responsibilities set forth in Section 3 of this Agreement, (ii) Employer and Employee have used their best efforts to obtain such approval, and (iii) this Agreement or Employee’s employment is not so approved by the Authorities, then this Agreement shall immediately terminate and shall be null and void, thus extinguishing any and all obligations of either party, subject to any surviving obligations of Employee under Sections 9, 10 and 21. (b) If applicable, Employer and Employee hereby covenant and agree that, in order for Employee to discharge the duties required under this Agreement, Employee must apply for or hold a license, registration, permit or other approval (the “License”) as issued by the Authorities pursuant to the terms of the relevant Gaming Act and as otherwise required by this Agreement. In the event Employee fails to apply for and secure, or the Authorities refuse to issue or renew Employee’s License, Employee, at Employer’s sole cost and expense, shall promptly defend such action and shall take such reasonable steps as may be required to either remove the objections or secure or reinstate the Authorities’ approval, respectively. The foregoing notwithstanding, if the source of the objections or the Authorities’ refusal to renew or maintain Employee’s License arise as a result of any of the acts, omissions or events described in Section 1(c) of this Agreement, then Employer’s obligations under this Section 8 also shall not be operative and Employee shall promptly reimburse Employer upon demand for any expenses incurred by Employer pursuant to this Section 8. (c) Employer and Employee hereby covenant and agree that the provisions of this Section 8 shall apply in the event Employee’s duties require that Employee also be licensed by governmental agencies other than the Authorities.

  • Closing Requirements Closing shall occur after approval of title commitment, as described hereinabove. a) At closing, Seller shall do the following: 1. Duly execute, acknowledge and deliver to Buyer, a Quit Claim Deed conveying the Property to Buyer, free and clear of all liens, claims, pledges and encumbrances. b) At closing, Buyer shall do the following: 1. Execute and provide at closing, all documents reasonably required by the City for closing. 2. Tender payment at closing for the purchase price and all associated closing costs described herein.

  • Forecasting Requirements 19.5.1 The Parties shall exchange technical descriptions and forecasts of their Interconnection and traffic requirements in sufficient detail necessary to establish the Interconnections necessary for traffic completion to and from all Customers in their respective designated service areas.

  • Covenants of Performance Measurement No interference. Registry Operator shall not interfere with measurement Probes, including any form of preferential treatment of the requests for the monitored services. Registry Operator shall respond to the measurement tests described in this Specification as it would to any other request from an Internet user (for DNS and RDDS) or registrar (for EPP). ICANN testing registrar. Registry Operator agrees that ICANN will have a testing registrar used for purposes of measuring the SLRs described above. Registry Operator agrees to not provide any differentiated treatment for the testing registrar other than no billing of the transactions. ICANN shall not use the registrar for registering domain names (or other registry objects) for itself or others, except for the purposes of verifying contractual compliance with the conditions described in this Agreement. PUBLIC INTEREST COMMITMENTS Registry Operator will use only ICANN accredited registrars that are party to the Registrar Accreditation Agreement approved by the ICANN Board of Directors on 27 June 2013 in registering domain names. A list of such registrars shall be maintained by ICANN on ICANN’s website. (Intentionally omitted. Registry Operator has not included commitments, statements of intent or business plans provided for in its application to ICANN for the TLD.) Registry Operator agrees to perform the following specific public interest commitments, which commitments shall be enforceable by ICANN and through the Public Interest Commitment Dispute Resolution Process established by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/picdrp), which may be revised in immaterial respects by ICANN from time to time (the “PICDRP”). Registry Operator shall comply with the PICDRP. Registry Operator agrees to implement and adhere to any remedies ICANN imposes (which may include any reasonable remedy, including for the avoidance of doubt, the termination of the Registry Agreement pursuant to Section 4.3(e) of the Agreement) following a determination by any PICDRP panel and to be bound by any such determination. Registry Operator will include a provision in its Registry-Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting Registered Name Holders from distributing malware, abusively operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting or otherwise engaging in activity contrary to applicable law, and providing (consistent with applicable law and any related procedures) consequences for such activities including suspension of the domain name. Registry Operator will periodically conduct a technical analysis to assess whether domains in the TLD are being used to perpetrate security threats, such as pharming, phishing, malware, and botnets. Registry Operator will maintain statistical reports on the number of security threats identified and the actions taken as a result of the periodic security checks. Registry Operator will maintain these reports for the term of the Agreement unless a shorter period is required by law or approved by ICANN, and will provide them to ICANN upon request. Registry Operator will operate the TLD in a transparent manner consistent with general principles of openness and non-discrimination by establishing, publishing and adhering to clear registration policies.

  • Operating Requirements Any operating and technical requirements that may be applicable due to Regional Transmission Organization, Independent System Operator, control area, or the Connecting Transmission Owner’s requirements, including those set forth in the Small Generator Interconnection Agreement. Operating Requirements shall include Applicable Reliability Standards.

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