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 1See 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. 2.1
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. Table 2 Software Subscription Unit of Measure Capacity Stackable Use Case Socket(s) Managed Nodes Red Hat CloudForms Managed Node: (Physical Node or Virtual Node) Socket-pair for each Physical Node or Sixteen (16) Virtual Nodes Physical Node: Yes Virtual Node: Yes Red Hat only provides Subscription Services for Red Hat CloudForms Software when deployed on (a) a System or Physical Node that is a server and (b) Virtual Nodes if they are running on-premise or on a Red Hat CloudForms enabled public cloud. Red Hat Enterprise Linux is the only supported operating system for Red Hat CloudForms Subscriptions.
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 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. Table 3
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.

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

  • 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 The following licensing requirements shall apply when the applicable Florida Statute mandates specific licensing for Contractors engaged in the type of work covered by this solicitation.

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

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

  • Grant Reporting Requirements The Grantee must submit the following reports to the Division. All reports shall document the completion of any deliverables/tasks, expenses and activities that occurred during that reporting period. All reports on grant progress will be submitted online via xxx.xxxxxxxxx.xxx. [INSERT PROGRESS REPORT DUE DATES]

  • Bidding Requirements The Advertisement or Invitation to Bid, Instructions to Bidders, Bid security form, if any, and the Bid form with any supplements.

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

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