Unit of Measure and Purchasing Requirements Sample Clauses

Unit of Measure and Purchasing Requirements for Red Hat OpenShift Container Platform. You must purchase the appropriate number and type of Software Subscription(s) for each Unit of Red Hat OpenShift Container Platform on your premise or elsewhere based on the capacity of such Unit as described in Table 1 below. Multiple Software Subscriptions may be “stacked” to account for the capacity of a given Unit. “Stacking” (or “Stackable”) means the application of more than one of the same Subscription to account for additional capacity. Red Hat OpenShift Container Platform for RHEL and Container Platform for RHEL are layered products and require a separate paid and active Software Subscription Red Hat Enterprise Linux for Virtual Datacenters with matching Support Levels for each Unit that deploys, installs, uses or executes such layered products. Table 1 Software Subscription Support Level Unit of Measure Capacity Stackable Socket(s) Virtual Nodes Red Hat OpenShift Container Platform Standard or Premium Virtual Guest 2 Cores One Virtual Guest Cores: Yes Virtual Guest: Yes Red Hat OpenShift Container Platform Standard or Premium Physical Node Socket-pair Unlimited Virtual Guests Physical Node: Yes Virtual Guest: N/A Red Hat OpenShift Container Platform for RHEL Standard or Premium Physical Node Socket-pair Unlimited Virtual Guests Physical Node: Yes Virtual Guest: N/A Container Platform for RHEL Standard or Premium Physical Node Socket-pair Unlimited Virtual Guests Physical Node: Yes Virtual Guest: N/A For purposes of this Exhibit 1.J, a “Socket-pair” is up to two sockets each occupied by a CPU on a Physical Node.
AutoNDA by SimpleDocs
Unit of Measure and Purchasing Requirements for Red Hat OpenShift Container Platform. You must purchase the appropriate number and type of Software Subscription(s) for each Unit of Red Hat OpenShift Container Platform on your premise or elsewhere based on the capacity of such Unit as described in Table 1 below. Multiple Software Subscriptions may be “stacked” to account for the capacity of a given Unit. “Stacking” (or “Stackable”) means the application of more than one of the same Subscription to account for additional capacity. Red Hat OpenShift Container Platform for RHEL and Container Platform for RHEL are layered products and require a separate paid and active Software Subscription Red Hat Enterprise Linux for Virtual Datacenters with matching Support Levels for each Unit that deploys, installs, uses or executes such layered products.
Unit of Measure and Purchasing Requirements for 1.1 OpenShift Enterpriseの計測ユニットおよび購入要求 OpenShift Enterprise
Unit of Measure and Purchasing Requirements. Table 1 sets forth the support level, Unit of measure, stacking capabilities and Supported Use Case for various Red Hat Storage Subscriptions. You must purchase the appropriate number and type of these Software Subscriptions based on the Unit and other parameters described in Table 1 below. In addition, the following terms apply:
Unit of Measure and Purchasing Requirements. Table 1 sets forth the Unit of measure and Supported Use Cases for Red Hat Cloud Infrastructure Subscriptions. You must purchase the appropriate number and type of these Software Subscriptions based on the Unit and Supported Use Cases described in Table 1 below. A Red Hat Cloud Infrastructure Software Subscription comes with a Red Hat CloudForms Software Subscription but if you are managing any virtual machines with the Red Hat Cloud Infrastructure Subscription that are not running on the same Physical Node as the active Red Hat CloudForms Software Subscription, you must purchase additional Red Hat CloudForms Subscriptions for such use.
Unit of Measure and Purchasing Requirements for Red Hat OpenShift CONTAINER PLATFORM

Related to Unit 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.

  • Initial Forecasts/Trunking Requirements Because Verizon’s trunking requirements will, at least during an initial period, be dependent on the Customer segments and service segments within Customer segments to whom CSTC decides to market its services, Verizon will be largely dependent on CSTC to provide accurate trunk forecasts for both inbound (from Verizon) and outbound (to Verizon) traffic. Verizon will, as an initial matter, provide the same number of trunks to terminate Reciprocal Compensation Traffic to CSTC as CSTC provides to terminate Reciprocal Compensation Traffic to Verizon. At Verizon’s discretion, when CSTC expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, Verizon will provide the number of trunks CSTC suggests; provided, however, that in all cases Verizon’s provision of the forecasted number of trunks to CSTC is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and CSTC’s previous forecasts have proven to be reliable and accurate.

  • Elsevier Open Access Terms and Conditions You can publish open access with Elsevier in hundreds of open access journals or in nearly 2000 established subscription journals that support open access publishing. Permitted third party re-use of these open access articles is defined by the author's choice of Creative Commons user license. See our open access license policy for more information. Terms & Conditions applicable to all Open Access articles published with Elsevier: Any reuse of the article must not represent the author as endorsing the adaptation of the article nor should the article be modified in such a way as to damage the author's honour or reputation. If any changes have been made, such changes must be clearly indicated. The author(s) must be appropriately credited and we ask that you include the end user license and a DOI link to the formal publication on ScienceDirect. If any part of the material to be used (for example, figures) has appeared in our publication with credit or acknowledgement to another source it is the responsibility of the user to ensure their reuse complies with the terms and conditions determined by the rights holder. Additional Terms & Conditions applicable to each Creative Commons user license:

  • 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:

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

  • WILEY OPEN ACCESS TERMS AND CONDITIONS Wiley Publishes Open Access Articles in fully Open Access Journals and in Subscription journals offering Online Open. Although most of the fully Open Access journals publish open access articles under the terms of the Creative Commons Attribution (CC BY) License only, the subscription journals and a few of the Open Access Journals offer a choice of Creative Commons Licenses. The license type is clearly identified on the article.

  • Metering Requirements Seller shall comply with all applicable rules in installing a meter appropriate for deliveries pursuant to the Full Buy/Sell or Excess Sale arrangement selected in paragraph 2.2, above, which can be electronically read daily by:

  • Federal Requirements Pertaining to Grants and Subrecipient Agreements A. Requirement to Have a Single Audit: In the case that this Agreement is a Grant that is funded in whole or in part by federal funds, the Subrecipient will complete the Subrecipient Annual Report annually within 45 days after its fiscal year end, informing the State of Vermont whether or not a Single Audit is required for the prior fiscal year. If a Single Audit is required, the Subrecipient will submit a copy of the audit report to the granting Party within 9 months. If a single audit is not required, only the Subrecipient Annual Report isrequired. For fiscal years ending before December 25, 2015, a Single Audit is required if the subrecipient expends $500,000 or more in federal assistance during its fiscal year and must be conducted in accordance with OMB Circular A-133. For fiscal years ending on or after December 25, 2015, a Single Audit is required if the subrecipient expends $750,000 or more in federal assistance during its fiscal year and must be conducted in accordance with 2 CFR Chapter I, Chapter II, Part 200, Subpart F. The Subrecipient Annual Report is required to be submitted within 45 days, whether or not a Single Audit is required.

  • Change Orders and Contract Amendments 33.1 The Procuring Entity may at any time order the Supplier through notice in accordance GCC Clause 8, to make changes within the general scope of the Contract in any one or more of the following:

  • Trunk Forecasting Requirements 14.2.1 Initial trunk forecast requirements. At least ninety (90) days before initiating interconnection in a LATA, Alltel shall provide Verizon a two (2)-year traffic forecast that complies with the Verizon Interconnection Trunking Forecast Guide, as revised from time to time. This initial traffic forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Interconnection Trunk groups in the LATA over the next eight (8) quarters.

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